ARCH: прикрепить debug MCP discovery

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

@@ -891,6 +891,36 @@ 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.
 
+## Progress Update - 2026-04-20 MCP Discovery Debug Attachment
+
+The tenth implementation slice of Big Block 5 added a debug/evidence attachment layer:
+
+- `assistantMcpDiscoveryDebugAttachment.ts`
+- `assistantMcpDiscoveryDebugAttachment.test.ts`
+
+It is now attached to:
+
+- address-lane response runtime debug;
+- deep-analysis debug payloads.
+
+This still does not execute MCP discovery automatically and still does not change the user-facing answer.
+
+It gives runtime and replay review a stable observable surface:
+
+- `assistant_mcp_discovery_entry_point_v1`;
+- `mcp_discovery_entry_status`;
+- `mcp_discovery_attempted`;
+- `mcp_discovery_hot_runtime_wired=false`;
+- `mcp_discovery_bridge_status`;
+- `mcp_discovery_answer_mode`;
+- business-fact/user-facing authorization flags;
+- clarification flag.
+
+Validation:
+
+- `npm test -- assistantMcpDiscoveryDebugAttachment.test.ts assistantDebugPayloadAssembler.test.ts assistantAddressLaneResponseRuntimeAdapter.test.ts assistantMcpDiscoveryRuntimeEntryPoint.test.ts` passed 13/13;
+- `npm run build` passed.
+
 ## Execution Rule
 
 Do not implement this plan as: