Scripts
Maintainer tooling for this repository's own CI, telemetry and validation. If you are onboarding or checking a product repo, you want redline init and redline verify instead.
Every script here runs in one of three places: this repo's own CI on every pull request, a scheduled workflow in the redline-metrics repo, or a maintainer's own terminal. None of them talk to a product repo directly — that's what the CLI is for.
validate.mjs →
Bundle self-check run by this repo's CI — manifest integrity, rule ids, ruleset/workflow files, the seed corpus.
assign-rule-ids.mjs →
Assigns a permanent id to every rule missing one, and rewrites standards/ in place.
render-self.mjs →
Renders this repo's own standards artifacts with the CLI's TypeScript renderer, profile javascript-typescript.
check-pins.mjs →
Re-resolves SHA-pinned third-party actions against the tag they claim.
score-seeds.mjs →
Scores a reviewer's PR comments against the seeded corpus: BLOCKER recall, false positives, rule attribution.
collect-telemetry.mjs →
Nightly central pull of review outcomes across the org — runs in the redline-metrics repo.
build-digest.mjs →
Builds the Monday Teams digest as an Adaptive Card — runs in the redline-metrics repo.
build-inbox.mjs →
Builds the org-wide prioritised PR inbox for GitHub Pages.
build-dashboard.mjs →
Builds the telemetry dashboard — runs in the redline-metrics repo.
build-registry.mjs →
Derives registry.json — the register of onboarded repositories — by walking the estate for .redline.json.
build-correlation.mjs →
Research: whether ignoring a finding cost anything. Refuses to report a rate the sample does not support.
build-roi.mjs →
The one page a finance stakeholder can read: what AI review cost, what it caught, and the DORA figures beside it.
build-baseline.mjs →
Computes the Phase 0 baseline every later roadmap phase is judged against, with every unavailable figure stating why.