Repository navigation
Conversation
JunjoSick
marked this pull request as ready for review
October 9, 2026 10:21
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 October 8 daily run used
ambiguous-disclosurefor every recent non-blocked article, including articles with no advertising disclosure. That made its 77-row queue look more suspicious than the underlying evidence.This PR adds precise review diagnostics and documents the completed 77-path investigation:
All 77 paths are absent from the current registries. Current RSS/API fragments were recovered for 76 candidates. Old and new classifiers returned identical decisions for all 76. GDC has three overlapping causes: styled PRE labels on all five, linked attribution footers on all five, and gallery STYLE elements on three.
Changes:
The accepted disclosure predicate, vocabulary, active-content veto, resource limits, timestamps, conflicts, and publisher gates are preserved. No baseline/state/registry/filter changes; no automatic publication of the recommendations. The 69 editorial assessments are evidence-based descriptions, not permanent keep overrides or proof that undisclosed payment never occurred.
Validation:
npm run cards:check,npm run check, bundle history verification and whitespace checks passed.Source workflow: https://github.com/JunjoSick/filtershosting/actions/runs/37775388864