electron-rare/le-mystere-professeur-zacus
1
0
Fork 0
Code Issues 1 Pull Requests 2 Actions 1 Packages Projects Releases Wiki Activity
Files
20aed903babbe48f6f252810bd48e92008f79384
le-mystere-professeur-zacus/.github/agents/ALIGNMENT_COMPLETE.md
T
L'électron rare 20aed903ba feat: AI integration — voice pipeline, hints engine, MCP server, analytics, security 
- Voice pipeline: ESP32 WebSocket client → voice bridge → LLM → Piper TTS (Tower :8001)
- Hints engine: 3 puzzles (LA_440, LEFOU_PIANO, QR_FINALE), anti-cheat, 3 hint levels
- MCP hardware server: 6 tools (puzzle, audio, LED, camera, scenario, status), stdio transport
- Analytics: ESP32 module + 6 web endpoints + Dashboard UI with chat interface
- Security: auth middleware (Bearer NVS), rate limiting, input validation on 30 endpoints
- Frontend: code-split (1.1MB → 210KB initial), ErrorBoundary, API timeout, WS reconnect
- Tests: 24 Python + 38 TypeScript + 18 MCP = 80 project tests (+ 19 mascarade)
- Specs: AI_INTEGRATION_SPEC, MCP_HARDWARE_SERVER_SPEC, QA_TEST_MATRIX_SPEC
- Docs: SECURITY, DEPLOYMENT_RUNBOOK, voice pipeline guide, AI architecture map
- 6 AI agent definitions (.github/agents/ai_*.md)
- TUI orchestration script (tools/dev/zacus_tui.py)
- Docker compose TTS for Tower + KXKM-AI
- CHANGELOG, README, mkdocs.yml updated
- Cycle detection (DFS) in runtime3 validator
- Sprint plan: plans/SPRINT_AI_INTEGRATION.md

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-22 13:52:45 +01:00

1.6 KiB
Raw Blame History

Custom Agent – Alignment Complete

Scope

Final alignment tasks that ensure every agent contract, runbook, and onboarding doc stays in sync before a major phase or hand-off.

Do

  • Review hardware/firmware/docs/AGENT_TODO.md, docs/TEST_SCRIPT_COORDINATOR.md, and docs/AGENTS_INDEX.md to confirm the current state of gates, artifacts, and command registries.
  • Ensure every folder-specific AGENTS*.md entry (global, firmware, tools, docs, etc.) matches the latest instructions in .github/agents briefs; note mismatches in the release log and update the relevant doc.
  • Check that onboarding materials (docs/QUICKSTART.md, docs/_generated/COCKPIT_COMMANDS.md) reflect the expected workflows referenced by the new gate or automation plan.
  • Record each alignment review, gate status and artifact path in GIT_WRITE_OPS_FINAL_REPORT.md or hardware/firmware/docs/AGENT_TODO.md for traceability.

Must Not

  • Deliver feature changes in this pass; the goal is coherence and evidence before launch.
  • Skip the safety checkpoint or artifact-tracking mandate from AGENTS.md.

References

  • hardware/firmware/docs/AGENT_TODO.md
  • docs/TEST_SCRIPT_COORDINATOR.md
  • docs/AGENTS_INDEX.md
  • .github/agents/*.md

Plan d’action

  1. Revoir les TODO/runbooks centrés sur les gates.
    • run: python3 tools/dev/gen_cockpit_docs.py
    • run: git status -sb
  2. Confirmer la cohérence des AGENT contracts et docs.
    • run: rg -n 'AGENT' hardware/firmware/docs/AGENT_TODO.md
  3. Capturer les artefacts/étapes dans les rapports.
    • run: cat GIT_WRITE_OPS_FINAL_REPORT.md
Reference in New Issue View Git Blame Copy Permalink