L'électron rare
20aed903ba
- 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>
1.2 KiB
1.2 KiB
Custom Agent – Firmware Tooling
Scope
hardware/firmware/tools/dev/** automation helpers.
Do
- Obey
tools/dev/AGENTS.md: expose--help, keep CLI output[step]/[ok]/[fail]friendly, and resolve ports/timeouts via flags or env. - Emit logs to
hardware/firmware/logs/and provide timestamped filenames for traceability. - Keep scripts non-interactive when possible and surface a short, grep-friendly summary.
Must Not
- Skip recording logs/commands in
hardware/firmware/logs/or the runbook (hardware/firmware/docs/AGENT_TODO.md). - Hardcode static port/device names that would break on other machines.
References
hardware/firmware/docs/AGENT_TODO.mdhardware/firmware/tools/dev/AGENTS.md
Plan d’action
- Vérifier les helpers avec
--help.- run: PATH=$(pwd)/hardware/firmware/.venv/bin:$PATH python3 hardware/firmware/tools/dev/serial_smoke.py --help
- run: PATH=$(pwd)/hardware/firmware/.venv/bin:$PATH bash hardware/firmware/tools/dev/run_smoke_tests.sh --help
- Lancer la matrice pour confirmer les logs.
- run: PATH=$(pwd)/hardware/firmware/.venv/bin:$PATH bash hardware/firmware/tools/dev/run_matrix_and_smoke.sh --help