АРЧ АП11 - Архитектура после регресса: Архитектура: централизовать organization authority в continuity policy для route, living-chat и data-scope

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

@@ -245,6 +245,12 @@ Latest continuity-authority convergence evidence after the current route pass:
   - deterministic organization-fact boundary replies can now trigger from grounded continuity even when `sessionScope.selectedOrganization` and `sessionScope.activeOrganization` are both empty at runtime entry;
   - the chat layer now records whether it entered with grounded continuity and which organization came from that continuity snapshot, making future saved-session review less blind;
   - proactive organization offer logic is now explicitly blocked when grounded address continuity already exists, so the chat layer does not re-offer company selection on top of an already grounded business session;
+- the next continuity-authority pass now centralizes `organization authority` in the shared continuity policy instead of letting route, living-chat, and data-scope reconstruct it independently:
+  - a single resolver now merges grounded address continuity, assistant-side living-chat scope memory, session scope, and clarification candidates into one authority object;
+  - route arbitration now consumes that shared authority for organization clarification continuation instead of rebuilding candidates and fallback selection locally;
+  - living-chat runtime now boots with the same authority object, so `knownOrganizations`, `selectedOrganization`, and `activeOrganization` no longer start from a different merge order than the route layer;
+  - data-scope active-organization recovery now also reads the same authority object, reducing one more history-scan seam that used to drift from route and chat;
+  - targeted tests now protect this precedence layer directly, including the case where assistant-side living-chat selection must outrank older grounded continuity without losing the grounded organization in the merged known set;
 - the first human-answer-shaping cleanup pass is now applied to heavy profile/aggregate exact answers:
   - `period_coverage_profile` and `document_type_and_account_section_profile` now start with a direct business-first lead (`Коротко: ...`) instead of service-flavored intros like `профиль собран` / `строк агрегата`;
   - the top block now states the business conclusion first and leaves ranked detail blocks below, which reduces the catalog-like feel without hiding the actual data;