Michael Dieringer 1fe40a2001 Add Node.js runtime prerequisite check before machine setup Step 3 ... Type B gap (Francis): bc-mcp-bridge.js is a Node.js script and the businesscentral MCP registration launches it via 'node ...', but nothing in the setup checklist ever verified Node was actually installed. Found missing on a fresh machine during a full developer onboarding today -- the bridge deployed fine, the MCP server registered fine, and then every connection attempt would have failed with a generic timeout instead of a clear "Node missing" message. Checked first: this is genuinely uncovered, not a documentation-clarity issue -- ~/.bc-mcp.config.json's path is already stated unambiguously everywhere it's referenced, so no rule needed there. This is a different, real gap: no prerequisite check existed at all.		2026-08-04 12:41:09 +02:00
..
machine	Deploy a shared MCP-tool permissions allowlist; detect legacy .claude/settings.json	2026-08-04 07:31:46 +02:00
templates	Fix all 6 confirmed findings from today's gap audit	2026-08-03 14:12:05 +02:00
bc-mcp-bridge.js	Ret bc-mcp: config-skabelon matcher broen + fejl svaelges ikke laengere	2026-08-01 00:18:37 +02:00
curabis-standard.agent.md	Add Node.js runtime prerequisite check before machine setup Step 3	2026-08-04 12:41:09 +02:00
support-users-onboarded.md	Fix all 6 confirmed findings from today's gap audit	2026-08-03 14:12:05 +02:00
sync-bcquality-knowledge.ps1	Deploy a shared MCP-tool permissions allowlist; detect legacy .claude/settings.json	2026-08-04 07:31:46 +02:00