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) - [Code Organization](#code-organization) - [WASM Build-Variant Pattern](#wasm-build-variant-pattern) - [Validation Architecture](#validation-architecture) - [Security Best Practices](#security-best-practices) - [Safe Output Messages](#safe-output-messages) - [Schema Validation](#schema-validation) - [YAML Compatibility](#yaml-compatibility) - [MCP Logs Guardrail](#mcp-logs-guardrail) - [Release Management](#release-management) - [Firewall Log Parsing](#firewall-log-parsing) - [Breaking CLI Rules](#breaking-cli-rules) - [Go Module Summaries](#go-module-summaries) ## 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_prog...