Skip to content

feat: capture partial native usage and prepare 0.106 candidate - #4672

Merged
EHotwagner merged 20 commits into
mainfrom
routine/passive-native-capture-20261018
Oct 18, 2026
Merged

EHotwagner merged 20 commits into
mainfrom
routine/passive-native-capture-20261018

Conversation

@EHotwagner

@EHotwagner EHotwagner commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

Explicitly selected native usage records can now be captured and reported locally before receiver access is available. The shared strict native decoder projects partial response observations with authentic thread/turn/response identity and optional counters. Unobserved item attribution, inventory, terminal status, model and cost remain unknown; these observations do not enter qualified item totals.

The producer reuses existing private atomic state and immutable spool. Exact pending intent survives uncertain enqueue; corrections retain stable identity and numeric predecessor delivery. Bounded eligible-head rotation preserves independent delivery when passive predecessors remain uncertain, and cursor advancement stops at actually attempted batches when the shared deadline expires. Partial tails, rotation, finite index/spool limits and source gaps remain explicit. Initial activate-remote --capture-only setup skips credential presence and reports the receiver unverified; later delivery retains existing credential and receipt gates.

The same source delivery prepares prospective coherent 0.106.0 candidate rails against accepted 0.105.0, including the current release journal binding and generated projections. Existing historical release behavior and the published/installed 0.105 binding remain preserved. This PR does not dispatch a candidate, publish, install, invoke a provider or establish receiver durability.

Core, focused workspace telemetry and full CLI assertions now run immediately after build, before browser/package/parity costs. The full coherent checks remain mandatory. TRX and blame sequence evidence are retained on failure; no memory dumps or larger job budget are enabled.

Validation: independent semantic and fixture review passed the repaired source and CI arrangement. On exact source b21abce7, retained hosted TRX confirms Core 1,211/1,211, focused workspace telemetry 25/25 and full CLI 740/740 passed, including both new Core and all sixteen new CLI Facts. Complete-reader duplicate/UTF8 controls retain the original strong path. Earlier focused failures exposed the exact passive refusal classification and a test targeting the wrong public guard; the fixes retain strict admission, canonical corrections and pending-byte recovery. The earlier opaque full-CLI failure remains unexplained under its original identity. Pure CI ordering/evidence controls passed 24/24 and change-completeness static controls passed 23/23. The complete coherent engine run 39121316546 passed, including package/browser/parity/mutation and standalone telemetry/lifecycle/BoardOps/kernel suites. Native tested tree 8bb92c627d6118bb23ec91ef80562538d61fb754 matches the source tree. Atlas citations match the repaired production source and distinguish preparation, installed behavior and receiver acceptance.

@EHotwagner
EHotwagner marked this pull request as draft October 18, 2026 08:42
@EHotwagner EHotwagner changed the title feat: capture partial native usage independently of delivery feat: capture partial native usage and prepare 0.106 candidate Oct 18, 2026
@EHotwagner
EHotwagner marked this pull request as ready for review October 18, 2026 11:37
@EHotwagner
EHotwagner merged commit 2e42faa into main Oct 18, 2026
139 of 146 checks passed
@EHotwagner
EHotwagner deleted the routine/passive-native-capture-20261018 branch October 18, 2026 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant