АРЧ АП11 - Архитектура после регресса: Архитектура: закрыть translit hybrid-entry seam в phase13 и закрепить routing в endpoint-регрессии

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

@@ -325,6 +325,10 @@ Still open after the accepted phase12 replay:
     - 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.
+  - the remaining translit root seam is now also closed in the same contour:
+    - transliterated supplier-tail wording no longer loses the causal tail during predecompose entry handling;
+    - live replay `address_truth_harness_phase13_hybrid_followup_authority_live_20260418_rerun4` is accepted with the translit root step returning `factual_with_explanation` and staying inside hybrid investigation routing;
+    - endpoint coverage now explicitly requires the translit account-60 tail question to keep every routed fragment in `hybrid_store_plus_live`, so future refactors cannot silently split the same question back into `hybrid + store_canonical`.
 
 ## Next Execution Slice (2026-04-18)
 
@@ -340,15 +344,17 @@ 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. 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.
+3. Reduce duplicated state reconstruction that still lives outside the shared continuity authority.
+4. Prove that non-flagship hybrid/deep-turn contours survive the same runtime contracts across more than one repaired scenario pack.
+5. Only after that, continue secondary answer-shaping cleanup where it materially affects acceptance.
+6. 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;
+- fewer hybrid/deep entry seams that still depend on fragment luck instead of explicit runtime contracts;
 - cleaner user-facing business answers on already-correct truth paths;
 - lower risk that new domains multiply orchestration chaos faster than capability growth.