fix: connect stored daily runtime records to QRS - #526
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
…-sync-20260929 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.
Daily runtime projections were saved to GCS but never delivered to the existing QRS daily-record endpoint. Add an optional, default-off publisher to the existing PAPER heartbeat step. It sends the exact stored body only after a confirmed new object, using the existing execution-evidence token and fixed target contract.
Existing objects and uncertain storage writes never trigger delivery. HTTP delivery has bounded sizes/timeouts, no redirects or retries, and validates the returned business date and target. Storage and sync outcomes remain separate. No production flags, credentials, bindings or trading settings are changed.
Validation: 49 targeted tests; Ruff, actionlint and diff check; independent Astra review. Actual Python-generated synthetic body passed the fixed QRS Worker contract (unauthorized 401, disabled 404, valid 200 with one write). Real production delivery remains unverified and disabled.