Repository navigation
test(ai): reduce repeated session and recovery setup - #317
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up for #240. This test-only slice removes repeated setup without reducing the supported backend matrix or changing production behavior, test selection, or the workflow.
Session repository instructions: 64 → 30 real agent turns with all four storage shapes × both checkpoint modes retained. Every combination learns a scope, reattaches a new Runtime, sees the updated rules before its first model request, and learns the second scope. Durable stores still close and reopen for a union readback. A shared SQL + frontier representative keeps same-runtime file overwrite/delete/recreate, unchanged-file reattach, fork, and independent-session isolation.
Evaluation: the single-lifetime graph-capture authorization test uses real in-memory Persistence; denial, grant, real execution and separate recapture denial remain. Existing SQLite/shared SQL reopen coverage stays.
Recovery: seed 258 real receipts in one setup transaction, then check committed order and status. The cancel receipt is still after the production page boundary; crash, recovery, cancellation and no-duplicate-effect assertions stay.
Human scoring: a single in-process decision/rescore test now uses real in-memory Persistence with explicit volatile opt-in. All decision, duplicate-submission and prior-result assertions remain; durable reopen and foreign-coordinator checks are unchanged.
Local scoped evidence on base
a642b557:Prior head
d3b8c9d6: Python 3.11 shard 4/5 reported xdistgw2 keyboard-interrupton an unchanged child-continuation test. Scoped reproductions did not reproduce it, and the log has no causal traceback. Do not treat this independently reviewed scoring change as a confirmed fix; evaluate the latest head's natural checks.This does not close #240.