Архитектура: сделать phase12 replay time-stable и вернуть честный acceptance gate для today-сценариев

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

@@ -439,6 +439,11 @@ Still open after the accepted phase12 replay:
   - item carryover precedence is now explicit in one helper: navigation focus item -> continuity active item -> explicit selected-object label from the current message;
   - this matters because selected-object follow-ups are one of the most fragile continuity seams in the product, and keeping their anchor mutation in the shared continuity layer reduces another chance that future inventory/domain expansion splits `focus_object` truth from follow-up carryover truth;
   - targeted continuity and transition regressions now protect both the helper layer and a real short selected-item follow-up path that must keep the `item` anchor without reopening company/date drift.
+- the next replay-gate honesty pass now removes a false red zone from the flagship saved-session proof:
+  - `address_truth_harness_phase12_wider_saved_session_pool` no longer hardcodes `2026-04-18` inside `today`-scoped steps for inventory root, payables, and receivables mirror follow-up;
+  - those steps now resolve `as_of_date` and visible date patterns through runtime placeholders (`{{runtime.today_iso}}`, `{{runtime.today_dot_regex}}`), so the replay verdict tracks real orchestration regressions instead of calendar drift;
+  - this matters because the flagship phase12 pack is one of the main top-level readiness indicators, and a date-stale spec was creating a false `partial` verdict even while `selected_object_continuity_ok`, `direct_answer_ok`, and the repaired continuity paths stayed green;
+  - the next live rerun after this pass should tell us whether any real runtime seam still exists in phase12 once the date-noise is removed.
 - the next continuity-authority pass now centralizes temporal backfill precedence for follow-up filters:
   - transition no longer holds a service-local block of `shouldBackfillPreviousDateScopeFromNavigation + six field-level ifs` for `as_of_date / period_from / period_to`;
   - shared continuity now owns that merge via `applyTemporalCarryoverFilters(...)`, while `shouldUseNavigationTemporalCarryover(...)` keeps the intent-family boundary explicit in one place;

docs/orchestration/address_truth_harness_phase12_wider_saved_session_pool.json

@@ -87,12 +87,12 @@
         "inventory_on_hand_as_of_date"
       ],
       "required_filters": {
-        "as_of_date": "2026-04-18",
+        "as_of_date": "{{runtime.today_iso}}",
         "organization": "ООО Альтернатива Плюс"
       },
       "required_direct_answer_patterns_any": [
         "(?i)на складе|остат",
-        "18\\.04\\.2026"
+        "{{runtime.today_dot_regex}}"
       ],
       "criticality": "critical",
       "semantic_tags": [
@@ -302,11 +302,11 @@
         "payables_confirmed_as_of_date"
       ],
       "required_filters": {
-        "as_of_date": "2026-04-18"
+        "as_of_date": "{{runtime.today_iso}}"
       },
       "required_direct_answer_patterns_any": [
         "(?i)долг к оплате|обязательств",
-        "18\\.04\\.2026"
+        "{{runtime.today_dot_regex}}"
       ],
       "criticality": "critical",
       "semantic_tags": [
@@ -326,10 +326,10 @@
       ],
       "required_direct_answer_patterns_any": [
         "(?i)дебитор",
-        "18\\.04\\.2026"
+        "{{runtime.today_dot_regex}}"
       ],
       "required_filters": {
-        "as_of_date": "2026-04-18"
+        "as_of_date": "{{runtime.today_iso}}"
       },
       "criticality": "critical",
       "semantic_tags": [