fix: preflight account snapshot delivery and constrain PAPER staging - #528
Merged
Merged
Conversation
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.
Reject invalid enabled snapshot-delivery configuration before acquiring credentials, fetching a snapshot or consuming the create-only daily archive slot. Extend the existing PAPER no-traffic staging path to accept only an explicit snapshot flag, bound to the main workflow SHA and existing admission/configuration/traffic readback checks. Legacy history candidate restrictions remain intact.
Validation: 70 daily snapshot tests plus 2 read-only entry tests; 24 admission tests; 42 workflow shell cases, 6 lifecycle cases and source-archive checks; actionlint, Ruff and syntax/diff checks. Independent Astra reviews passed, including an in-memory old/new delivery-preflight reproduction and seven actual workflow dispatch guards.
No deployment, traffic switch, scheduler change or trading activation is performed by merging this PR. Unknown delivery outcomes are not retried, existing daily objects are not overwritten, and the new flag does not grant execution authority.