SILVER/NODEDC_1C
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Архитектура: протянуть shared root-frame authority в assistantService follow-up glue

Browse Source
This commit is contained in:
dctouch
2026-04-19 09:01:28 +03:00
parent 62f9bad750
commit a71e1352be
4 changed files with 126 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ARCH/11 - architecture_turnaround/11 - continuity_stabilization_plan_2026-04-17.md
+9
View File
@@ -406,6 +406,15 @@ Still open after the accepted phase12 replay:
- the adapter now imports and uses only the shared builders from `assistantMemoryRecapPolicy`, which makes the live chat branch structurally closer to a single owner for grounded contextual replies;
- targeted `assistantLivingChatRuntimeAdapter` and `assistantMemoryRecapPolicy` tests stay green after the cleanup, and backend build remains green;
- live reruns on `phase14` and `phase15` on `2026-04-19` surfaced partial top-level status only because the packs still pin `inventory today` expectations to `2026-04-18`; the repaired contextual reply contours themselves stayed semantically clean, which confirms this pass as owner reduction rather than a new runtime regression.
- the next continuity-authority pass now removes one more duplicate root-frame owner from `assistantService` follow-up glue:
- `assistantService.extractAddressCarryoverAnchor(...)` no longer reconstructs anchor resolution from raw `anchor_value_* / extracted_filters` using its own local precedence order;
- `assistantService.findRecentInventoryRootFrame(...)` no longer rebuilds inventory root carryover from `detected_intent + extracted_filters` as a separate local parser;
- both seams now consume the shared continuity helpers:
- `resolveAddressDebugAnchorContext(...)`
- `buildInventoryRootFrameFromAddressDebug(...)`
- this matters because follow-up carryover in the top-level service now reads the same root-frame authority that already owns `root_filters / root_anchor / current_frame_kind`, instead of keeping a service-local fallback that could silently prefer drilldown `extracted_filters` over the real `address_root_frame_context`;
- targeted `assistantAddressFollowupContext` and `addressInventoryRootFrameRegression` suites are green after the move, including a new regression that explicitly proves `root_filters` come from `address_root_frame_context.root_filters` rather than from stale drilldown `extracted_filters`;
- this pass strengthens continuity convergence in the top-level orchestration glue without introducing a new case-specific branch.
## Next Execution Slice (2026-04-18)