Read receiver readiness from the existing protected runner - #332
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
…donly request Co-Authored-By: Codex <noreply@openai.com>
…-error-codes-20261002 Co-Authored-By: Codex <noreply@openai.com> # Conflicts: # scripts/publish_binance_account_facts.py # tests/test_binance_account_facts.py
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.
Scope
Use the existing protected runner and dedicated sync credential for a single GET readiness diagnosis against the existing receiver. The manual workflow requires the exact current main revision. It does not query the broker, read reports, send a POST, change synchronization gates or retry.
Keep unknown publisher HTTP failures actionable through bounded status and fixed response-shape labels. Response text, credentials, private identity and arbitrary errors are not printed; successful publishing behavior is unchanged.
Verification
The real receiver failure remains unqualified. Synchronization is disabled while the new read-only diagnostic is prepared.