Repository navigation
test(ai): avoid disk setup for live evaluation policy checks - #320
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.
Refs #240. Exercise the five single-lifetime Evaluation effect-policy combinations with real in-memory Persistence and explicit volatile opt-in. All existing deny/read_only/live, next-step dynamic tool/MCP, status and side-effect assertions remain. Keep the separate SQLite admission/reopen and retry/fork coverage; no production or CI configuration changes.
One matched local check with CPython 3.11.18 on
c9f92ebd: same five nodes 22.32s → 4.28s, both 5 passed. Three focused durable/volatile guards passed. Configured Ruff and diff check passed. This is test-node evidence, not whole-CI wall time. Natural CI pending; does not close #240.