yaze/AGENTS.md

Inter-Agent Protocol (Lean)

1. Read the board (docs/internal/agents/coordination-board.md) before starting.
2. Log your intent (task, scope, files) on the board with your agent ID.
3. Answer requests tagged to your ID.
4. Record completion/handoff with a short state note.
5. For multi-day work, use docs/internal/agents/initiative-template.md and link it from your board entry.

Agent IDs (shared with Oracle-of-Secrets/.claude/agents)

Use these canonical IDs (scopes in docs/internal/agents/personas.md and .claude/agents/*):

Agent ID	Focus
ai-infra-architect	AI/agent infra, z3ed CLI/TUI, gRPC/network
backend-infra-engineer	Build/packaging, CMake/toolchains, CI reliability
docs-janitor	Docs, onboarding, release notes, process hygiene
imgui-frontend-engineer	ImGui/renderer/UI systems
snes-emulator-expert	Emulator core (CPU/APU/PPU), perf/debugging
test-infrastructure-expert	Test harness, CTest/gMock, flake triage
zelda3-hacking-expert	Gameplay/ROM logic, Zelda3 data model
GEMINI_FLASH_AUTOM	Gemini automation/CLI/tests
CODEX	Codex CLI assistant
OTHER	Define in entry

Legacy aliases (CLAUDE_CORE, CLAUDE_AIINF, CLAUDE_DOCS) → use imgui-frontend-engineer/snes-emulator-expert/zelda3-hacking-expert, ai-infra-architect, and docs-janitor.

Helper Scripts (keep it short)

Located in scripts/agents/:

• run-gh-workflow.sh, smoke-build.sh, run-tests.sh, test-http-api.sh Log command results + workflow URLs on the board for traceability.

Escalation

If overlapping on a subsystem, post REQUEST/BLOCKER on the board and coordinate; prefer small, well-defined handoffs.