Repository navigation
fix(context): preserve ownership across startup, routes and resume - #129
RecursiveIntell wants to merge 2 commits into
Conversation
૮ >ﻌ< ა ci reviewran on 6f9d470 — fix(context): preserve effective MoA mode and absent-compres
|
|
Reviewed follow-up to failed Python slices 10/12 and 4/12: outer MoA host/cache/primary snapshot now records effective chat_completions mode while internal aggregator transport remains unchanged. Restore skips only explicitly absent ( Accepted scope: 80 focused passes and 43 compatibility passes with two missing-SDK failures preserved. Two separate fake constructor passes are not SDK qualification. Independent review and exact forward/reverse replay accepted. Original 122-case c91f789 checkpoint remains historical evidence rather than qualification of the advanced tree. Original external native containment failure remains unqualified; no native replay or installed/provider execution occurred. Published draft head |
This branch has not been deployed
1 participant
Explicit
ri-context-governorselection could silently fall back to stockcompression or hide startup binding errors. Model handoffs also omitted output
reserve and could leave the host on a refused route while its governor kept the
previous budget. Startup now uses the existing strict Ares factory; initialization,
switching, fallback and restoration forward reserve through each engine's API.
The governor caps its effective target at the resolved input window and retains
its refusal for exhausted input budget, including configured 1.05M intent when
that window permits it.
A shared host rollback preserves the last accepted route/client/credential/cache
state on refusal. Internal fallback continuation counts an originating
rate-limit/billing failure once while distinct later failures still advance
backoff. SessionDB is passed to Ares startup so cold compression/rebase ancestry
keeps its existing logical governor root and branch/delegate boundaries.
Validation: original corrected baseline reproduces 18 failures with 10 passing
controls; V3 recorded 28 focused and 94 compatibility passes. Independent
reviews then identified and preserved R1/R2, each with red counterexamples.
Final V5 replayed all original 122 cases with unchanged recorded harness/assertions/fakes:
122 passed, 0 failed across eight files. It also records 12 focused passes and seven
existing backoff/cooldown passes;
the preceding rollback delta recorded 27 affected compatibility passes. A
legacy local-availability check failed on a missing optional Anthropic SDK and
is retained; its three cases pass with narrowly scoped task-only external
fakes. Native SDK/provider behavior remains unqualified. Locked canonical
runner, one worker, zero file retries; exact source/fixture hashes and producer
receipts retained. Forward/reverse patches round-trip exact base/final trees.
Independent final exact-source review passed on tree
c91f789f87651bb29e067db9f83af0c3c29fa39e; R1/R2 are resolved. Core alone publishes thisdraft against freshly checked main and normal CI; no merge or deployment is authorized.
The installed runtime, native allocator/admission/receipt protocol, key authority,
memory transport and rebase compiler are unchanged. Final serialized input,
provider capacity and installed/native readiness are separate qualification gates.
Exact base
04997747879d54a242941d344c3a38293c307076, treecbabd9591dc00fdf8deed90aeb3e8b1dc5bd2ebc. Reverse patch SHA25628ef936aeaad7201bb9a492dff2fec526a5fef5dffc00ca1dc6a15c8362a8a5erestores this source delta. No installed/native rollback accompanies publication. CTX-04/05 remain findings-only and outside this draft. Hosted CI is a separate gate.