Snippet Fidelity v0.2.0 turns the source-to-clipboard prototype into an installable release gate for documentation projects.
Highlights
-
Published as
snippet-fidelity:npm install --save-dev snippet-fidelity npx playwright install chromium npx snippet-fidelity audit https://docs.example.com/
-
Added a reusable composite GitHub Action. Pin
WLDKK/snippet-fidelity@v0and supply either a source-aware config or a live URL. -
Added Markdown, JSON, and JUnit report support to the Action workflow.
-
Added clean package-consumer and Action smoke verification to the release gate.
-
Expanded the dated competitor ledger with Doc Detective, Playwright Clipboard, and custom Playwright tests.
-
Published a responsible public-site pilot study covering Astro Starlight, Material for MkDocs, and Doc Detective.
Reliability fixes found during the pilot
- Automatic discovery now excludes hidden code blocks and copy controls left mounted by tab and responsive layouts.
- Hover-revealed controls remain eligible for fidelity checks.
- Copy probes activate the selected control directly, so unrelated visual overlap is not misreported as a clipboard-fidelity failure.
- npm package metadata now preserves the installed
snippet-fidelitycommand, and the release gate requires the generated.binshim.
Verification
- Formatting and TypeScript checks passed.
- 20 tests passed, including real Chromium end-to-end coverage.
- The composite Action passed in GitHub Actions against the repository fixture.
- The package passed pack inspection and a clean tarball install.
- The public npm package was installed in a fresh directory and its command reported
0.2.0.
Evidence boundaries
Rendered-DOM discovery is intended for reconnaissance. A dependable merge gate should declare canonical text or a canonical UTF-8 source file. This release supports Chromium only and does not test pointer hit-targeting or native paste applications.
See the GitHub Action guide, pilot study, and changelog for details.