Архитектура: вернуть company activity assessment в address lane и убрать ложный organization anchor из root-scoped carryover

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

@@ -362,6 +362,20 @@ Still open after the accepted phase12 replay:
   - active organization bootstrap now flows through selected organization, navigation organization, and shared continuity authority in one place instead of keeping a second callback-shaped fallback branch beside the authority object;
   - `assistantService.resolveSessionOrganizationScopeContext(...)` no longer passes that legacy callback into the runtime adapter, which reduces one more orchestration seam where old and new organization owners could drift;
   - targeted organization-scope, data-scope, and route regressions remain green after the change, and wide saved-session replay `address_truth_harness_phase12_wider_saved_session_pool_live_20260418_rerun9` remains accepted `20/20`, which is the critical proof that this bootstrap convergence did not reopen the flagship continuity path.
+- the next replay-breadth pass now proves a different late-session contour instead of replaying only the flagship chain:
+  - a new live pack `address_truth_harness_phase14_counterparty_tail_resume` validates `data-scope meta -> explicit company selection -> counterparty docs -> short-name follow-up -> inventory today -> account 60 -> inventory aging -> historical inventory -> organization activity analytics` inside one shared session;
+  - the first draft of this pack exposed one real architecture seam rather than another continuity collapse: `Как ты оценишь деятельность компании?` after grounded organization activity-age was still falling into `living_chat` because the route depended too much on the L0 gate and not enough on the resolved supported intent;
+  - `addressCounterpartyIntentSignals` now treats company-activity assessment wording as the same `counterparty_activity_lifecycle` contour instead of leaving it as unsupported meta chat;
+  - `assistantRoutePolicy` now recovers the address lane from a supported resolved intent even when the initial L0 gate stays negative, so the system no longer loses a real business contour just because the low-level shape classifier stayed `unsupported`;
+  - targeted counterparty UTF-8 and route-policy regressions now explicitly protect this seam, including the exact late-tail wording `Как ты оценишь деятельность компании?`;
+  - live replay `address_truth_harness_phase14_counterparty_tail_resume_live_20260418_rerun2` is accepted `10/10`, which is the critical proof that replay breadth is now broader than the original flagship chain and that late-session organization analytics no longer depend on ambient chat luck.
+
+- the next transition-authority pass now closes a subtler root-scoped carryover seam inside the shared follow-up path:
+  - `assistantService.buildAddressFollowupOffer(...)` now reads follow-up anchor metadata through the shared continuity helper instead of reconstructing it from yet another local `addressDebug` parser;
+  - `assistantTransitionPolicy` no longer promotes assistant-side `organization authority` into `previous_anchor_type=organization` when a root-scoped inventory pivot intentionally sanitizes the selected-item carryover and keeps only the restored root frame;
+  - this matters because `root_context_only` VAT pivots from inventory drilldown should preserve restored organization/date filters without pretending that restored scope is itself a user-selected follow-up anchor;
+  - targeted `assistantAddressFollowupContext` and `assistantTransitionPolicy` suites are now green after the fix, explicitly protecting the `inventory drilldown -> VAT pivot` regression where selected-item carryover must be removed while the inventory root company/date window remains intact;
+  - live replay `address_truth_harness_phase12_wider_saved_session_pool_live_20260418_rerun10` remains accepted `20/20`, which is the critical proof that this anchor-sanitization convergence did not reopen the flagship saved-session continuity path.
 
 ## Next Execution Slice (2026-04-18)