ARCH: добавить entry point MCP discovery

This commit is contained in:
2026-04-20 10:16:13 +03:00
parent 95f3fdafbb
commit 76db8ef012
4 changed files with 302 additions and 0 deletions
@@ -867,6 +867,30 @@ Validation:
- `npm test -- assistantMcpDiscoveryTurnInputAdapter.test.ts assistantMcpDiscoveryPolicy.test.ts assistantMcpCatalogIndex.test.ts assistantMcpDiscoveryPlanner.test.ts assistantMcpDiscoveryRuntimeAdapter.test.ts assistantMcpDiscoveryPilotExecutor.test.ts assistantMcpDiscoveryAnswerAdapter.test.ts assistantMcpDiscoveryRuntimeBridge.test.ts` passed 37/37;
- `npm run build` passed.
## Progress Update - 2026-04-20 MCP Discovery Runtime Entry Point
The ninth implementation slice of Big Block 5 added a runtime entry point:
- `assistantMcpDiscoveryRuntimeEntryPoint.ts`
- `assistantMcpDiscoveryRuntimeEntryPoint.test.ts`
This entry point is still not wired into the hot assistant answer path.
It gives runtime integration a single safe call boundary:
- builds discovery turn input from assistant turn meaning, predecompose contract, and raw wording;
- skips supported exact turns before any discovery execution;
- executes the runtime bridge only for discovery-eligible turns;
- keeps `hot_runtime_wired=false`;
- exposes `discovery_attempted`, `entry_status`, `turn_input`, and optional `bridge`.
This is the first complete non-hot pipeline from current-turn context to guarded MCP discovery result.
Validation:
- `npm test -- assistantMcpDiscoveryRuntimeEntryPoint.test.ts assistantMcpDiscoveryTurnInputAdapter.test.ts assistantMcpDiscoveryPolicy.test.ts assistantMcpCatalogIndex.test.ts assistantMcpDiscoveryPlanner.test.ts assistantMcpDiscoveryRuntimeAdapter.test.ts assistantMcpDiscoveryPilotExecutor.test.ts assistantMcpDiscoveryAnswerAdapter.test.ts assistantMcpDiscoveryRuntimeBridge.test.ts` passed 40/40;
- `npm run build` passed.
## Execution Rule
Do not implement this plan as: