feat(digest): filter routine standards notices and flag stale runs - #186
Merged
Merged
Conversation
Drop the four routine notices (exact text, notice level only), collapse a notice repeated across repositories to one counted line, and show each repo's run date. A run older than the commit the standards-check-v1 tag points at, resolved at runtime, is flagged as predating current rules; an unresolvable tag is stated in the output. Summary counts reflect the rows shown. The Not checked section is unchanged.
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.
The live digest (issue #170, 2026-10-04 run) listed 160 standards rows; 159 were noise. This filters them and makes stale runs visible.
Changes
group_by, and it also covers the next notice GitHub repeats across the fleet. Warnings never collapse.standards-check-v1tag in smartwatermelon/github-workflows is flagged "predates current rules".standards.shresolves the tag at runtime (ref, then the annotated tag object, then the commit date). If it cannot, the section says "Rules date unknown" with the reason; it does not drop the flag silently.A repo whose rows were all filtered still appears, with its run date, so a stale run stays visible (this is the nightowlstudiollc/kebab-tax case: its 2026-09-19 run predates the
.claude/rule). Summary counts reflect the rows shown. "Not checked" is unchanged.Tests
New cases in
test-standards.sh, with fixtures for the tag. Known-bad cases: a warning-level "no workflows" row survives; a stale run whose only row was filtered is flagged; an unresolvable tag is reported.run-tests.shpasses (109 assertions) andshellcheck -S infois clean on the three changed shell files.Does not close any issue.