Files
computer-playbook/docs/contributing/tools
kevinveenbirkenbachandClaude Opus 5 e7fadf02fe ci(workflows): name workflows for GitHub's lists
Every scheduled workflow opened with an alarm clock, so the Actions list
read as a column of identical icons that said nothing about the run. The
clock now lives in run-name behind github.event_name == 'schedule', where
it marks the one thing it can mark: a run nobody triggered. The name says
what the run does, in two or three words.

The dispatch menu shows names in one narrow column and truncates them, so
a new lint caps a workflow_dispatch name at 25 characters and points the
longer, explanatory wording at run-name, which carries no such limit.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-22 11:18:54 +02:00
..
…
…

Tooling guides 🧰

This directory contains contributor guidance for project tools. Its scope is how repository-standard tools should be used, when they apply, and where they fit into the wider workflow.

CLI Helpers 🛠️

Helper Purpose
port.md cli contributing network ports suggest: propose free host-bound ports inside PORT_BANDS.<scope>.<category>.
address.md cli contributing network address suggest: propose free per-role subnets gap-first within established umbrella blocks.