SILVER/NODEDC_1C
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

ARCH: добавить runtime bridge MCP discovery

Browse Source
This commit is contained in:
dctouch
2026-04-20 10:09:37 +03:00
parent b4865f36b1
commit 9d6e7066e0
4 changed files with 318 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ARCH/11 - architecture_turnaround/14 - semantic_dialog_authority_recovery_plan_2026-04-19.md
+26
View File
@@ -818,6 +818,32 @@ Validation:
- `npm test -- assistantMcpDiscoveryPolicy.test.ts assistantMcpCatalogIndex.test.ts assistantMcpDiscoveryPlanner.test.ts assistantMcpDiscoveryRuntimeAdapter.test.ts assistantMcpDiscoveryPilotExecutor.test.ts assistantMcpDiscoveryAnswerAdapter.test.ts` passed 29/29;
- `npm run build` passed.
## Progress Update - 2026-04-20 MCP Discovery Runtime Bridge
The seventh implementation slice of Big Block 5 added a runtime bridge contract:
- `assistantMcpDiscoveryRuntimeBridge.ts`
- `assistantMcpDiscoveryRuntimeBridge.test.ts`
This bridge is still not wired into the hot assistant answer path.
It composes the already separated discovery layers into one orchestration-facing contract:
- planner;
- isolated pilot executor;
- human-safe answer draft;
- bridge status;
- explicit `hot_runtime_wired=false`;
- business-fact answer authorization flags;
- clarification and unsupported-state flags.
This gives future runtime integration a single object to attach to debug/evidence flow without letting discovery silently become a user-facing answer path.
Validation:
- `npm test -- assistantMcpDiscoveryPolicy.test.ts assistantMcpCatalogIndex.test.ts assistantMcpDiscoveryPlanner.test.ts assistantMcpDiscoveryRuntimeAdapter.test.ts assistantMcpDiscoveryPilotExecutor.test.ts assistantMcpDiscoveryAnswerAdapter.test.ts assistantMcpDiscoveryRuntimeBridge.test.ts` passed 33/33;
- `npm run build` passed.
## Execution Rule
Do not implement this plan as: