fix(risk): require gs:// claim store for live account-owner fence - #460
Merged
Conversation
Fail closed when non-dry-run would use a local claim backend that cannot fence across instances. Co-Authored-By: Claude <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Co-Authored-By: Codex <noreply@openai.com>
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
1 participant
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.
Summary
gs://.Test plan
PYTHONPATH=. pytest tests/test_runtime_composer.py(2 passed)gs://before enabling any new live pathMade with Cursor
Codex takeover validation (2026-09-08)
The four request tests failed because their successful live fixtures had no durable store URI. This correction changes tests only: synthetic gs:// configuration for the four mocked-cycle cases, plus an actual entrypoint rejection test asserting missing storage never enters the execution cycle. The production gate is unchanged. Fresh regression: 4 failed before; request/composer suites 37 passed and 9 subtests after. Ruff, diff and uv pip check passed. Full local suite: 467 passed, 1 skipped, 1 unrelated existing strategy_runtime consecutive_losses expectation failure; the same test also fails on the env-sync branch without the EX-05 change, and its implementation/test/dependency paths are unchanged. Linux required CI remains the CI result of record. No merge, deployment, provider, broker or account operations.