АРЧ АП11 - Архитектура после регресса: Архитектура: исправить deep-turn normalizer schema contract и вернуть hybrid follow-up authority в phase13 replay

docs/ARCH/11 - architecture_turnaround/11 - continuity_stabilization_plan_2026-04-17.md

@@ -315,6 +315,16 @@ Still open after the accepted phase12 replay:
   - this matters because route, living-chat, data-scope, and early session-scope bootstrap are now closer to the same organization merge order instead of keeping a separate pre-route branch with its own drift risk;
   - targeted tests now explicitly protect the case where assistant-side continuity authority is present in prior assistant debug even when legacy history helpers are empty;
   - live replay `address_truth_harness_phase12_wider_saved_session_pool_live_20260418_rerun4` remains accepted `20/20`, which is the critical proof that this authority convergence did not reopen the wider saved-session path.
+- the next architecture pass exposed and fixed a deeper hybrid-investigation contract break outside the flagship address chain:
+  - phase13 replay showed that hybrid anomaly/tails questions were no longer failing only on follow-up continuity; the root entry itself had stopped entering the hybrid lane because deep-turn normalization was calling the normalizer with `promptVersion=address_query_runtime_v1`;
+  - the model was already returning valid `normalized_query_v2_0_2` payloads for these questions, but the runtime validated them as legacy `v1`, discarded the parsed normalized object, and then dropped into claim-bound clarification with empty `fragments / route_summary`;
+  - deep-turn normalization now forces an actual normalizer contract (`promptVersion=normalizer_v2_0_2`, `schemaVersion=v2_0_2`) unless the caller already supplied a normalizer-family prompt explicitly;
+  - this is a real architecture fix, not a case patch: deep-turn no longer inherits a user-facing address runtime prompt as if it were a normalizer schema contract;
+  - targeted deep-turn normalization tests now protect this seam directly, including the case where an address-lane prompt would previously have caused silent `v1` validation and total fragment loss;
+  - live replay `address_truth_harness_phase13_hybrid_followup_authority_live_20260418_rerun3` is now accepted:
+    - root supplier tails anomaly questions re-enter `hybrid_store_plus_live` with grounded fragments and non-empty deterministic route summaries;
+    - narrowing follow-up for `2020-06 / account 60` now keeps hybrid/batch routing instead of collapsing into empty clarification;
+    - the broader hybrid investigation contour is therefore back under explicit runtime authority rather than ambient luck.
 
 ## Next Execution Slice (2026-04-18)
 
@@ -330,13 +340,15 @@ This next slice should be executed in the following order:
 
 1. Finish continuity authority convergence in the hot runtime path.
 2. Widen saved-session replay coverage beyond the already repaired flagship chains.
-3. Tighten human answer shaping on long exact answers without reintroducing template drift.
-4. Only after that, begin controlled domain-by-domain expansion toward the multi-domain stage.
+3. Prove that non-flagship hybrid/deep-turn contours survive the same runtime contracts instead of silently inheriting wrong prompt/schema assumptions.
+4. Only after that, continue secondary answer-shaping cleanup where it materially affects acceptance.
+5. Only after that, begin controlled domain-by-domain expansion toward the multi-domain stage.
 
 Current explicit goals for this slice:
 
 - fewer owners independently reconstruct `active context`;
 - more replay breadth before any large expansion claim;
+- fewer hidden runtime contract mismatches between entry prompts, schema validation, and deep-turn orchestration;
 - cleaner user-facing business answers on already-correct truth paths;
 - lower risk that new domains multiply orchestration chaos faster than capability growth.