Архитектура: убрать мертвые local reply builders из living-chat adapter и оставить единый shared policy owner

This commit is contained in:
2026-04-19 08:55:28 +03:00
parent 6d131b0e30
commit 62f9bad750
3 changed files with 7 additions and 218 deletions
@@ -400,6 +400,12 @@ Still open after the accepted phase12 replay:
- `resolveAssistantLivingChatMemoryContext(...)` now carries explicit `contextualAnswerInspectionFollowup` plus the grounded address debug that should be inspected, so living-chat reads one shared policy context instead of reconstructing this class from raw mode reason and direct continuity fields inline;
- this matters because living-chat is now less of a hidden parallel owner of grounded session semantics, and future answer-inspection / recap / capability follow-up fixes can land in one shared policy seam instead of splitting again across adapter-local builders;
- targeted recap and living-chat runtime tests stay green after this move, and live replay `address_truth_harness_phase15_answer_inspection_followup_live_20260418_rerun7` remains accepted `9/9`, which is the critical proof that the policy convergence did not reopen the phase15 contour.
- the next living-chat owner-reduction pass now removes one more dead parallel builder layer from the adapter itself:
- `assistantLivingChatRuntimeAdapter` no longer keeps local deterministic builders for inventory-history capability, memory recap, or selected-object answer inspection alongside the already active shared policy implementations;
- those builders were no longer on the active runtime path, but their presence kept a false second owner of the same user-facing behavior inside the adapter and increased the chance that future fixes would land in dead code instead of the shared policy seam;
- 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.
## Next Execution Slice (2026-04-18)