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/firmware_core.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.1 KiB
Raw Blame History

Custom Agent – Firmware Core

Scope

All files under hardware/firmware/**.

Do

  • Follow hardware/firmware/AGENTS.md: keep build/smoke gates in tools/dev, track structural changes in docs, and update hardware/firmware/docs/AGENT_TODO.md with build/smoke state.
  • Run PlatformIO builds via ./build_all.sh or the individual matrix before major changes.
  • Document UI Link, LittleFS, and I2S status in hardware/firmware/docs/AGENT_TODO.md along with artifact guidance.

Must Not

  • Commit logs or artifacts; keep them under hardware/firmware/logs/ or artifacts/ and mention their paths in reports.

References

  • hardware/firmware/AGENTS.md
  • hardware/firmware/docs/AGENT_TODO.md

Plan d’action

  1. Construire la matrice Firmware.
    • run: bash hardware/firmware/build_all.sh
    • run: bash hardware/firmware/tools/dev/run_matrix_and_smoke.sh
  2. Noter les statuts UI Link/LittleFS/I2S et loggers.
    • run: bash hardware/firmware/tools/dev/run_smoke_tests.sh
    • run: python3 hardware/firmware/tools/dev/serial_smoke.py --role auto --wait-port 3 --allow-no-hardware
Reference in New Issue View Git Blame Copy Permalink