Repository navigation
Keep evidenced registry badges and docs links when they cannot be checked - #30
Merged
Merged
Conversation
pekral
force-pushed
the
fix/23-keep-evidenced-badges
branch
from
November 12, 2026 13:33
f3d0c45 to
caeb8b6
Compare
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.
What this changes
In update mode, a registry badge or documentation link the existing README already carries now counts as evidence when its slug matches the manifest. It is kept and reported as kept but unverified when the registry or site cannot be reached, instead of being dropped. A documented package keeps only its first example in Quick start and delegates the rest to that docs link.
Closes #23
Why
Scenario 1 ran offline and dropped the Packagist version and downloads badges because publication could not be confirmed, and removed the docs link while writing its mechanics inline. The evidence policy did not count the maintainer's own README as evidence, so any offline run lost them. A badge or link is now dropped only on evidence against it (a mismatched slug, or a check that ran and failed), never because a check could not run.
Checks
node --test tests/repository.test.mjspassesnode --test tests/evals/*.test.mjspasses (33/33 together)CHANGELOG.mdupdated under the current unreleased headingSKILL.mdis changed everywhere it appears inreferences/(evidence-policy.md,validation-checklist.md,readme-structure.md)tests/scenarios.md, and the run recorded in itshost coverage log
Claims this adds to the documentation
claude -p "Update the README for this repository." --permission-mode acceptEdits --setting-sources project, skill copied into the workspace). Evidence: the badge row is version, license, Tests, downloads with theacme/sluggerslug; Quick start holds the first example alone; the docs link is kept as## Documentation; the handover names the Packagist badges and docs link as unverified. An intermediate run with only the evidence-policy change kept the badges and link but still inlined a second example and a mechanics paragraph, which is why the documented-package rule was tightened too.