ARCH: добавить candidate ответа MCP discovery

docs/ARCH/11 - architecture_turnaround/14 - semantic_dialog_authority_recovery_plan_2026-04-19.md

@@ -945,6 +945,31 @@ 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 assistantMcpDiscoveryDebugAttachment.test.ts assistantAddressOrchestrationRuntimeAdapter.test.ts assistantAddressLaneResponseRuntimeAdapter.test.ts assistantDebugPayloadAssembler.test.ts` passed 61/61;
 - `npm run build` passed.
 
+## Progress Update - 2026-04-20 MCP Discovery Response Candidate
+
+The twelfth implementation slice of Big Block 5 added a guarded response-candidate layer:
+
+- `assistantMcpDiscoveryResponseCandidate.ts`
+- `assistantMcpDiscoveryResponseCandidate.test.ts`
+
+This layer still does not replace the final user-facing assistant answer.
+
+It converts a validated MCP discovery entry point into a future-use answer candidate:
+
+- Russian reply text for confirmed, inferred, unknown, limitation, and clarification sections;
+- `hot_runtime_wired=false`;
+- `eligible_for_future_hot_runtime`;
+- `must_keep_internal_mechanics_hidden=true`;
+- internal primitive/query/runtime mechanics are filtered out;
+- unsupported discovery output is not exposed as a future hot candidate.
+
+This creates the final guarded buffer needed before any explicit answer replacement policy can be introduced.
+
+Validation:
+
+- `npm test -- assistantMcpDiscoveryResponseCandidate.test.ts assistantMcpDiscoveryRuntimeEntryPoint.test.ts assistantMcpDiscoveryDebugAttachment.test.ts assistantMcpDiscoveryAnswerAdapter.test.ts assistantMcpDiscoveryPilotExecutor.test.ts` passed 17/17;
+- `npm run build` passed.
+
 ## Execution Rule
 
 Do not implement this plan as: