Архитектура: убрать legacy active-organization callback из session-scope bootstrap и упростить organization authority path

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

@@ -357,6 +357,11 @@ Still open after the accepted phase12 replay:
   - this matters because data-scope probing, organization selection bootstrap, and the broader continuity layer are now closer to one canonical organization merge order instead of keeping a separate debug-field collector inside the scope policy;
   - targeted data-scope and organization-scope tests now protect that known organizations still include assistant-side authority, grounded address context, and free-text fallback organizations;
   - wide saved-session replay `address_truth_harness_phase12_wider_saved_session_pool_live_20260418_rerun8` remains accepted `20/20`, which is the critical proof that this data-scope convergence did not reopen the flagship saved-session path.
+- the next session-bootstrap pass now removes one more legacy callback seam from the organization scope adapter:
+  - `assistantOrganizationScopeRuntimeAdapter` no longer depends on a separate `findLastAssistantActiveOrganization(...)` callback even though it already computes shared continuity-backed organization authority internally;
+  - 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.
 
 ## Next Execution Slice (2026-04-18)