MaksTinyWorkshop d002435f03 docs(mcp): add NUC + Tailscale central hosting design (chantier, non démarré) ...

Capture le design abouti d'un MCP central:
- besoin: 1 instance, lecture+écriture, sans clone local sur chaque machine
- hébergement NUC en HTTP (FastMCP streamable-http), exposition via Tailscale (pas de WAN)
- écriture centralisée: ALLOW_WRITE=1 côté NUC, plus de conflit multi-machine
- workflow capitalisation à seuil: accumulation -> triage_capitalization() au-delà de N -> rapport -> validation humaine
- source de vérité données: Git (origin), NUC = clone de référence

Statut: PISTE non figée (pas dans 40_decisions_et_archi.md). Reste-à-faire listé.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-25 01:33:40 +02:00

..

design_nuc_tailscale.md

docs(mcp): add NUC + Tailscale central hosting design (chantier, non démarré)

2026-06-25 01:33:40 +02:00

implementation_plan.md

leadtech-bmad-mcp: close lot 3 rollout and gates config

2026-03-31 16:12:42 +02:00

knowledge_metadata.md

leadtech-bmad-mcp: close lot 1 and implement lot 2 index

2026-03-31 15:57:09 +02:00

mcp_v1.md

docs(mcp-rollout): align rollout doc with Phase 2 partielle reality

2026-05-07 07:40:34 +00:00

pilot_bmad_10_stories.md

bmad: wire leadtech mcp pilot into agent customizations

2026-03-31 16:28:10 +02:00

quickstart_dev_local.md

leadtech-bmad-mcp: close lot 3 rollout and gates config

2026-03-31 16:12:42 +02:00

rollout_bmad_advisory.md

feat(observability): scaffold Phase 2 tracking for Leadtech MCP rollout

2026-05-07 08:06:04 +00:00