[mottihoresh]

Adds CLAUDE.md, the repo's agent instructions. The repo had none; it links to ARCHITECTURE.md and PRD.md rather than repeating them.

Rules:

• Release facts: never say a feature is "in firmware vX" without git merge-base --is-ancestor <commit> firmware-vX in OpenSkyhawk. Firmware before 1.0.0 is test-only; 1.0.0 is the first public release. Background: the firmware-v0.2.0 tag was cut 7 minutes before feat(firmware)!: v1.0 freeze fixes — firmware version on the bus, config structs, pinned dependencies (#295) OpenSkyhawk#359, so "from firmware v0.2.0" in feat: read and show the Gateway's link-health counters (GET_DIAG) #169 and feat: show each board's firmware version and warn on a major mismatch #171 was wrong.
• Minimum firmware: a client PR that depends on a firmware change names the firmware commit or release it needs, in the PR body.
• No magic numbers: every address, code, enum and layout value comes from npm run sync; if the sync doesn't extract it yet, extend scripts/sync-a4ec.ts (example: NODE_FORGET_REQ_ADDR, feat: Forget also clears the board on the Gateway #188). Points to the existing _ACFT_NAME exception in ARCHITECTURE.md so the two files agree.
• Ticket closure: each box ticked with its evidence ("— #PR") or moved to a named follow-up before a ticket closes.
• Firmware claims get a review: ticket text stating firmware behaviour, wire format or release facts goes to the firmware (OpenSkyhawk) session before it reaches the user.

Verification

• Docs only; no code changes.
• npx prettier --check CLAUDE.md passes.
• The ARCHITECTURE.md anchor link matches its "Firmware values come from npm run sync" heading.

🤖 Generated with Claude Code