You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f736676
Browse filesBrowse the repository at this point in the historyBrowse files
Add selected native closes and synchronous current-point execution (#250)
* Add selected native closes and synchronous current-point execution
* Respect the decision floor for current execution and retain v13 CI proof
* Recognize exact engine RTTI in sanitized ABI epoch rejection
* Derive ABI provider epoch from archive symbols, not the --library role
The sanitized cross-epoch RTTI allowance inferred the provider's engine
epoch from whether the runtime path equalled --library. In
--old-rejections-only mode the authenticated e60 v13 archive may itself be
supplied as --library, so a current v14 caller's expected rejection was
misclassified as same-epoch and its exact-owner RTTI refused (false
failure, never a false acceptance).
Read the epoch from the archive's defined BacktestEngine symbols instead,
memoized per archive, and keep the allowance decision in one tested
predicate: exact caller-owner RTTI is tolerated only for a sanitized
cross-epoch negative link. Full-matrix behaviour is unchanged.
Add a tooling test for symbol-derived epochs (none/several refused) and
for the allowance predicate across both directions and sanitizer states.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_015wvgEP9WUyEQhta7ZDqUB4
* Fence every epoch-14 engine shape against the v13 providers and close review gaps
The settlement ABI checker skipped the engine storage-declaration, virtual-
inventory and most layout-word comparisons whenever the provider epoch
differed from the current one. With every real provider at epoch 13 that
bypass would have let any later epoch-14 commit change BacktestEngine
storage, its vtable or the compared aggregate layouts without an epoch bump,
even though all of those compare equal today.
Compare them unconditionally: storage declarations, the virtual inventory
and every emitted layout word must match the v13 providers; a mismatch
names the differing words. The four native headers that the v14 slice
deliberately changed are the only enumerated exemptions for the v13->v14
transition, each recorded in the receipt with both digests and pinned to
its reviewed bytes, so a further change within v14 fails until the epoch
is bumped and the pin re-recorded. Hoist the per-link decision into
link_outcome() with a really memoized provider_engine_for(), and record the
provider epoch on every link row.
Tests: three tooling tests drive the review-2 --old-rejections-only alias
configuration through the production link decision (memo reads once per
archive), the header exemption matrix and the full layout comparison, plus
one for the exempted-header pins. The waiting-owner current-execution
refusal is asserted exactly through both preview and execute_current, and
the resting replay contract gains a selected BindOpenings close scenario
(cohort of two, unrelated opening untouched, cancelled cohort close carrying
OpeningsClose authority) compared across two hosts at every boundary.
Docs: the settlement ABI fixture guide lists all three real providers, the
--v13-receipt flag and what the v13->v14 comparison actually checks;
abi-stability.md states the exemption and pin rules.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_013y1CvsXqLFMRgAW7TXJQMs
---------
Co-authored-by: Claude Fable 5.1 <[email protected]>
0 commit comments