АРЧ ЮИ - остановка прогона через гуй

This commit is contained in:
2026-04-18 18:14:30 +03:00
parent 9710d81676
commit 12550606bb
39 changed files with 1783 additions and 93 deletions
@@ -278,6 +278,38 @@ Latest continuity-authority convergence evidence after the current route pass:
- this is still not the end of shaping work: heuristic debt shortlists and some residual catalog-style blocks still need the same cleanup;
- this pass does not yet finish full single-owner continuity, but it narrows one of the remaining seams where route arbitration and scope memory could disagree about whether the session was still grounded.
Latest phase12 wider saved-session replay evidence after the current architecture pass:
- a new live replay `address_truth_harness_phase12_wider_saved_session_pool_live_20260418_rerun3` is accepted end-to-end with `20/20` steps green;
- this wider pack now proves one shared assistant session across a longer mixed path:
- first-turn smalltalk with proactive company offer;
- explicit company fixation;
- capability-meta interruption;
- inventory roots and historical roots;
- selected-object provenance and sale follow-up;
- selected-item -> VAT-period bridge;
- revenue aggregate pivot;
- payables/receivables polarity mirror;
- counterparty documents and short-name follow-up;
- account-60 tails;
- inventory aging and company activity-age;
- the replay exposed one real remaining seam before final acceptance:
- colloquial smalltalk entry reached the correct `living_chat + proactive_scope_offer` lane, but the first answer still depended on raw LLM preamble and leaked irrelevant generic chat (`Какой сегодня день?`);
- the fix was to convert `first-turn smalltalk + proactive organization offer` into a deterministic guarded entry path instead of trusting uncontrolled LLM preamble above the offer;
- colloquial living-chat detection is now unicode-safe and no longer depends on Cyrillic `\\b` boundaries that silently fail in JavaScript regex;
- this matters architecturally because another formerly ambient monolith behavior is now an explicit runtime contract:
- first-turn proactive company entry is controlled by runtime authority, not prompt luck;
- the broader saved-session pack now proves that organization authority, continuity carryover, and top-level chat entry survive one longer real-user trajectory rather than only the earlier flagship chains.
Still open after the accepted phase12 replay:
- replay breadth is now better than before, but still not yet broad enough to call multi-domain expansion low-risk by default;
- the biggest remaining architecture risk is no longer the original continuity collapse, but the unfinished convergence toward one true single-owner session authority across every hot path;
- the next execution slice should therefore continue prioritizing:
- more saved-session and multi-trajectory replay breadth;
- less duplicated state reconstruction in route / transition / living-chat glue;
- controlled expansion only after those broader proofs stay green.
## Next Execution Slice (2026-04-18)
The project is now moving from: