feat: publish recorded account snapshots to QRS - #525
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.
Connects the existing daily PAPER snapshot recorder to the authenticated QRS account-facts endpoint behind a default-off flag. Only an explicitly newly created immutable history object is published, with exactly the saved body and no extra broker query. Existing objects and unknown storage outcomes are skipped.
Publishing uses a dedicated token, HTTPS, no redirects or retries, bounded responses and exact target/observation confirmation. A publishing failure preserves the successful recording status and reports the unconfirmed synchronization separately. No production values, account permissions or collectors are enabled.
Validation: 66 snapshot tests, Ruff, Actionlint and diff check passed. Independent Astra review passed, including compatibility with the fixed QRS c537d0a validator and incorrect/unknown acknowledgement cases. Real publication and account identity verification remain untested.