Summary
crawl-sim has a publish workflow, but it does not currently have CI that gates merges on test, smoke, and cross-platform script validation.
That gap is directly related to several defects found in the public-release audit:
- macOS-only
robots.txt regression
- broken compare report generation on the happy path
- report-generator security regression
These are exactly the kinds of failures that a lightweight CI matrix should catch before release tags are cut.
Current state
- tests exist and pass locally (
npm test)
- publish workflow exists
- branch protection on
main is effectively off
- no mandatory CI status check is present for release-critical paths
Suggested improvements
- Add a CI workflow that runs on push and pull_request.
- Run at least:
npm test
- a compare-report smoke test
- an HTML-report generation smoke test
- Add a small OS matrix for shell portability:
ubuntu-latest
macos-latest
- Wire branch protection to require the CI workflow before merging.
Why this matters
This repo is positioning itself as a public OSS tool and npm/plugin install target. Release confidence should come from automation, not just local verification.
Acceptance criteria
Summary
crawl-simhas a publish workflow, but it does not currently have CI that gates merges on test, smoke, and cross-platform script validation.That gap is directly related to several defects found in the public-release audit:
robots.txtregressionThese are exactly the kinds of failures that a lightweight CI matrix should catch before release tags are cut.
Current state
npm test)mainis effectively offSuggested improvements
npm testubuntu-latestmacos-latestWhy this matters
This repo is positioning itself as a public OSS tool and npm/plugin install target. Release confidence should come from automation, not just local verification.
Acceptance criteria
npm testis part of CI.mainis protected by required CI status checks.