developer

# Developer Instructions Use this reference for gh-aw technical specs and development guidelines across code organization, validation, security, and implementation patterns. ## Table of Contents - [Operational Command Playbook](#operational-command-playbook) - [Capitalization Guidelines](#capitalization-guidelines) - [Sub-Skills](#sub-skills) ## Operational Command Playbook Use this section for the detailed day-to-day command flow that was intentionally removed from `AGENTS.md` to keep first-run ambient context small. ### Validation checkpoints Run validation in tiers — catch compile errors early, defer slow tests to the final pass only. 1. **After each significant code edit** (fast, <5s — catch compile errors immediately) ```bash make build && make fmt ``` 2. **Before every intermediate `report_progress` call** (fast, <30s — no tests) ```bash make agent-report-progress-no-test ``` 3. **Before the FINAL `report_progress` call** (change-scoped, includes impacted Go tests) ```bash make agent-report-progress ``` 4. **Before final handoff when time allows** ```bash make agent-finish ``` > **Key rule:** Run `test-unit` only before the **final** `report_progress` call, not before intermediate saves. The pre-PR targets scope formatting, linting, tests, and workflow drift checks to the branch changes. > **Timeout budget:** `make agent-report-progress` should normally finish in under 30 seconds. Workflow source or compiler changes additio...