Files
le-mystere-professeur-zacus/.github/agents/game.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.2 KiB
Raw Blame History

Custom Agent Game Content

Scope

game/scenarios/**, game/prompts/**, and derived documents regenerated from YAML sources.

Do

  • Treat game/scenarios/*.yaml as the single source of truth for story points and content.
  • Run python3 tools/scenario/validate_scenario.py game/scenarios/zacus_v2.yaml and python3 tools/scenario/export_md.py game/scenarios/zacus_v2.yaml after edits.
  • Re-run audio/printable manifest validators when scenario IDs or references change.

Must Not

  • Edit generated docs without first updating the scenario YAML.
  • Change IDs without syncing every reference (audio, docs, printables).

References

  • game/AGENTS.md

Plan daction

  1. Valider le scénario source et régénérer les docs.
    • run: python3 tools/scenario/validate_scenario.py game/scenarios/zacus_v2.yaml
    • run: python3 tools/scenario/export_md.py game/scenarios/zacus_v2.yaml
    • run: python3 tools/scenario/verify_runtime3_pivots.py game/scenarios/zacus_v2.yaml
  2. Revalider les manifestes audio et printables après toute mise à jour.
    • run: python3 tools/audio/validate_manifest.py audio/manifests/zacus_v2_audio.yaml
    • run: python3 tools/printables/validate_manifest.py printables/manifests/zacus_v2_printables.yaml