fix: reduce routine health notification noise - #358
Merged
Merged
Conversation
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
Quiet normal scheduled health receipts; preserve real strategy/trading notifications and actionable/unverified conditions.
No bot, recipient, token, repository variable, schedule, permission or dependency pin changes. Unified multi-platform delivery remains a separate phase. No live notification, broker query, order, drill or deployment was triggered.
Verification
Root reviewed the exact patch and independently reran 61 new offline regressions. Matching baseline policy failures are disclosed: two tests require an unavailable local calendar package; the full local suite is not claimed green. Exact pinned receipt module compatibility was separately verified. Required repository CI must pass before normal merge.
Reviewed base: 3bae23e
Reviewed head: 84d34b9
Exact candidate tree: eb37b11cfdefe6f83e292fb9f9f156e0b86b866d
Real adoption and the next natural scheduled cycle remain unverified.