Repository navigation
Conversation
This was referenced Nov 4, 2026
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
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.
AI assistance
OpenAI Codex (GPT-6.1 Sol). Independent review is pending with the established review-and-merge bot.
What changed
Use one bilingual asset-management error body for Schwab cycle errors with the unified flag on or off, attention alerts, receipt checks, candidate-coverage warnings, and the runtime guard. Retain unknown order state instead of inferring that no order was submitted. Exclude raw dashboard/account/provider text from the delivered body.
Preserve approved-gate classification, routine candidate deferral, execution results, existing incident reservations, and delivery acknowledgement semantics. Reset the display context on exceptions and isolate concurrent workers.
How verified
Why
The producer already defers ordinary cycles, but its errors and monitor paths still used different titles and could fall back to legacy account dashboards. This implements only step 5 of the approved notification plan.
Risk
High: runtime notification presentation paths. No execution or financial gate changes. No production settings, switch, Secret, IAM, workflow, deployment, label, or merge changes. Existing ACK and restart behavior is retained; no new retry path is introduced. Runtime adoption and authentic delivery remain unproved.
Shared contract pin follow-up
The step-1 branch
fix/notify-unify-1-shared-contracthad no published open PR at the readback before this publication. This patch implements the plan's fixed body using the current frozen QPK localization/redaction helpers. It does not hand-edit vendor snapshots or change dependency pins. Follow up with the published step-1 formatter and its exact dependency revision through the existing synchronization path; this PR does not claim that the new shared formatter is pinned.Publication checks
Complete tracked candidate tree:
publication-check/2.0-advisory, build83d9d1130377, advisory exit 0; 1678 findings across 1663 matching lines. This advisory does not change native CI or review gates. The reviewed diff contains no real credentials. PR text before this evidence section: 0 matches. First 20 complete-tree matches below are masked by the shared checker/display masker.