plumbbob 0.8.13 → 0.8.17

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "plumbbob",
   "displayName": "PlumbBob",
-  "version": "0.8.13",
+  "version": "0.8.17",
   "description": "Attention-first build process — driver skills + a CLI that keep you the decider: guidance on the work, a latch on the record.",
   "author": { "name": "Rob McLarty", "email": "hello@robmclarty.com", "url": "https://robmclarty.com" },
   "homepage": "https://github.com/robmclarty/plumbbob#readme",

package/dist/lib/agents.js

@@ -327,7 +327,7 @@ function skipWarnings(heading, skipped) {
 // is the author's error and is refused loud. Slot *contents* stay lenient (D61): a
 // slot value may be one name or a list, and blanks/non-strings drop rather than
 // refuse, because bindings feed a spawn, not a git-gating parse.
-export function parseHarness(raw) {
+function parseHarness(raw) {
     if (!isObject(raw)) {
         return { ok: false, error: 'harness.json must be a JSON object.' };
     }

package/dist/lib/check.js

@@ -31,12 +31,15 @@ export async function detectGate(root) {
     }
 }
 // Checkride's always-on repo checks: the adapters its doctor reports even for
-// an EMPTY directory (links, the pnpm-audit security scan, and the
-// publint/attw package-shape probes). They exercise the repo's plumbing, not
-// its code — a gate made only of these green-lights every checkpoint while the
-// human believes their work is being checked. Coupled to checkride's built-in
-// set by construction; the doctor.test.ts probe pins the coupling.
-const ALWAYS_ON_ADAPTERS = ['links', 'pnpm-audit', 'publint', 'attw'];
+// an EMPTY directory — the built-in `links` slot, the pnpm-audit security
+// scan, the publint/attw package-shape probes, and (checkride 0.5.0's
+// publish bundle) the built-in pack/smoke/snippets slots, which resolve on any
+// package with no tool config of their own. They exercise the repo's plumbing
+// or its shipped artifact, not its code — a gate made only of these green-lights
+// every checkpoint while the human believes their work is being checked. Coupled
+// to checkride's built-in set by construction; the check.test.ts and
+// doctor.test.ts probes pin the coupling.
+const ALWAYS_ON_ADAPTERS = ['links', 'pnpm-audit', 'publint', 'attw', 'pack', 'smoke', 'snippets'];
 // The detection rule, shared by `start`'s probe and doctor's callout: some tool
 // slot beyond the always-on family has an adapter — i.e. checkride can see the
 // CODE (a tsconfig, a test runner, a linter…), not just the repo.

package/dist/lib/intent.js

@@ -149,6 +149,26 @@ export function parseBuildTitle(content) {
     }
     return '';
 }
+const SCOPE_HEADER = /^\*\*Scope:\*\*\s*(.*)$/;
+const SCOPE_PLACEHOLDER = /^<.*>$/;
+// The build's default Conventional-Commit scope (D4): the `**Scope:**` header
+// field authored once at plan time, its value read verbatim off the line with any
+// trailing `<!-- ... -->` guidance note stripped. An unfilled placeholder — an
+// empty value or an angle-bracket placeholder like `<feature>` — parses as absent
+// (D7), so a freshly scaffolded, not-yet-edited build falls through to the next
+// scope rung (the build slug) rather than landing commits scoped `(<feature>)`.
+// null when the header is absent entirely — the pre-D4 shape (C2 back-compat).
+export function parseBuildScope(content) {
+    for (const line of content.split('\n')) {
+        const m = SCOPE_HEADER.exec(line.trim());
+        if (m === null) {
+            continue;
+        }
+        const value = (m[1] ?? '').split('<!--')[0]?.trim() ?? '';
+        return value === '' || SCOPE_PLACEHOLDER.test(value) ? null : value;
+    }
+    return null;
+}
 export function scrapeBullets(content, heading) {
     const lines = content.split('\n');
     const start = lines.findIndex((l) => l.trim() === heading);

package/dist/lib/orient.js

@@ -73,10 +73,11 @@ export function markStepDone(intent, n) {
     })
         .join('\n');
 }
-// Open questions still open: `- Q\d+:` lines that do not say "resolved".
+// Open questions still open: `- Q\d+:` openers that do not say "resolved". The
+// opener may carry a slug-at-birth gloss — `- Q2 (some-slug): ...` (D3) — which
+// the count reads through; sub-lines (`*plain:*`/`*lean:*`) never match.
 export function parseOpenQuestions(intent) {
-    return sectionLines(intent, '## Open questions').filter((l) => /^- Q\d+:/.test(l.trim()) && !/resolved/i.test(l))
-        .length;
+    return sectionLines(intent, '## Open questions').filter((l) => /^- Q\d+(?: \([^)]+\))?:/.test(l.trim()) && !/resolved/i.test(l)).length;
 }
 // Open parked items: `- [ ]` lines under `## Park list` (the `park` verb's format).
 // A harvested item is flipped to `- [x]` by `/pb-harvest` and no longer counts; the

package/dist/verbs/checkpoint.js

@@ -13,7 +13,7 @@ import { activeBuild, buildFolder, buildLogPath, buildScope, bumpStepStat, check
 import { runCheck } from "../lib/check.js";
 import { checkLatch } from "../lib/latch.js";
 import { markStepDone, parseSteps } from "../lib/orient.js";
-import { parseStepSeam, scopeDrift } from "../lib/intent.js";
+import { parseBuildScope, parseStepSeam, scopeDrift } from "../lib/intent.js";
 import { conventionalSubject, subjectFromTitle, withMarker } from "../lib/commitmsg.js";
 import { appendToSection, checkpointLogLine } from "../lib/buildlog.js";
 import { AT_BOUNDARY, syncBuildLogState } from "../lib/buildlogsync.js";
@@ -101,11 +101,12 @@ function checkpointPlan(root, args) {
     process.stdout.write(`plumbbob: plan committed — ${sha.slice(0, 9)}. Baseline → plan → steps.\n`);
     return 0;
 }
-// The plan commit's CLI-owned subject (D68): `chore(<scope>): plan`, the scope drawn
-// from the active build's slug (a bare `chore: plan` when none resolves). The
-// `plumbbob plan` identifier rides the body marker, not the subject.
+// The plan commit's CLI-owned subject (D68): `chore(<scope>): plan`, the scope
+// resolved through the build-default fallback chain (a bare `chore: plan` when
+// none resolves). The `plumbbob plan` identifier rides the body marker, not the
+// subject.
 function planSubject(root) {
-    return conventionalSubject({ type: 'chore', scope: buildScope(activeBuild(root)), description: 'plan' });
+    return conventionalSubject({ type: 'chore', scope: buildDefaultScope(root), description: 'plan' });
 }
 // Step resolution (D3): explicit arg > in-flight STEP file > first undone step in
 // intent.md. Returns null when none can be determined. A `-m` value is a message,
@@ -210,18 +211,36 @@ function statsSuffix(root, step) {
     return parts.length > 0 ? parts.join(', ') : null;
 }
 // The CLI-owned, deterministic commit subject (D68): a Conventional `type(scope):
-// description`. The scope comes from the active build's slug; the type and wording
-// come from the step's title — an author-written prefix (`fix(parser): …`) is honoured
-// verbatim, a bare title defaults to `feat`. A titleless step falls back to
-// `chore(<scope>): checkpoint`. The `plumbbob`/`step N` identifiers ride the body
-// marker, not the subject; a `-m` override or `--body` prose is a separate concern.
+// description`. The type and wording come from the step's title — an author-written
+// prefix (`fix(parser): …`) is honoured verbatim, a bare title defaults to `feat`.
+// The scope falls back through the chain (D3): the title's own `(scope)` wins
+// (handled inside `subjectFromTitle`), else `buildDefaultScope`. A titleless step
+// falls back to `chore(<scope>): checkpoint`. The `plumbbob`/`step N` identifiers
+// ride the body marker, not the subject; a `-m` override or `--body` prose is a
+// separate concern.
 function subjectForStep(root, step) {
-    const scope = buildScope(activeBuild(root));
+    const scope = buildDefaultScope(root);
     const title = titleForStep(root, step);
     return title !== null && title.trim().length > 0
         ? subjectFromTitle(title, 'feat', scope)
         : conventionalSubject({ type: 'chore', scope, description: 'checkpoint' });
 }
+// The build-default Conventional scope (D3/D4): the `**Scope:**` header field in
+// intent.md when authored and filled, else the build slug (D68's original rung,
+// now the penultimate one), else null — a bare subject (C2 back-compat: a build
+// with neither field behaves exactly as before D4).
+function buildDefaultScope(root) {
+    try {
+        const fromHeader = parseBuildScope(readFileSync(intentPath(root), 'utf8'));
+        if (fromHeader !== null) {
+            return fromHeader;
+        }
+    }
+    catch {
+        // no intent.md yet — fall through to the slug rung.
+    }
+    return buildScope(activeBuild(root));
+}
 function titleForStep(root, step) {
     try {
         return parseSteps(readFileSync(intentPath(root), 'utf8')).find((s) => s.n === step)?.title ?? null;

package/dist/verbs/finish.js

@@ -9,8 +9,9 @@
 import { appendFileSync, existsSync, readFileSync, rmSync } from 'node:fs';
 import { join } from 'node:path';
 import { commit, findRepoRoot, isDirty, stageAll } from "../lib/git.js";
-import { buildScope, checkpointsPath, clearTick, hasSession, readStats, reportPath, resolveBuild, seamPath, setGrant, sidecarDir, spikePath, stepPath, } from "../lib/sidecar.js";
+import { buildScope, checkpointsPath, clearTick, hasSession, intentPath, readStats, reportPath, resolveBuild, seamPath, setGrant, sidecarDir, spikePath, stepPath, } from "../lib/sidecar.js";
 import { conventionalSubject, withMarker } from "../lib/commitmsg.js";
+import { parseBuildScope } from "../lib/intent.js";
 export function finish(cwd, args = []) {
     const root = findRepoRoot(cwd);
     if (root === null || !hasSession(root)) {
@@ -34,7 +35,7 @@ export function finish(cwd, args = []) {
     if (isDirty(root)) {
         stageAll(root);
     }
-    const sha = commit(root, subject(slug), withMarker('plumbbob finish', bodyArg(args) ?? undefined));
+    const sha = commit(root, subject(root, slug), withMarker('plumbbob finish', bodyArg(args) ?? undefined));
     // Clear the control state: the in-flight markers first, then the session sentinel
     // last (so "no session" flips exactly at the end). Deleting STATE also drops the
     // cursor (D28) — cursor and session share the one file now, so a single delete does
@@ -54,12 +55,27 @@ export function finish(cwd, args = []) {
         'Run `/pb-plan` (or `plumbbob start "<title>"`) to frame the next goal.\n');
     return 0;
 }
-// The CLI-owned final-commit subject (D68): `chore(<scope>): finish`, the scope drawn
-// from the build's slug (a bare `chore: finish` when none resolves, e.g. `--local`),
-// mirroring the plan/step Conventional shape so one grammar spans the whole history.
-// The `plumbbob finish` identifier rides the body marker, not the subject.
-function subject(slug) {
-    return conventionalSubject({ type: 'chore', scope: buildScope(slug), description: 'finish' });
+// The CLI-owned final-commit subject (D68): `chore(<scope>): finish`, the scope
+// resolved through the same build-default fallback chain as plan/step subjects
+// (D3/D4): the `**Scope:**` header field, else the build slug, else bare (e.g.
+// `--local`). The `plumbbob finish` identifier rides the body marker, not the
+// subject.
+function subject(root, slug) {
+    return conventionalSubject({ type: 'chore', scope: buildDefaultScope(root, slug), description: 'finish' });
+}
+// See checkpoint.ts's twin of this helper (same fallback, this verb's own `slug`
+// resolution instead of the active-build cursor).
+function buildDefaultScope(root, slug) {
+    try {
+        const fromHeader = parseBuildScope(readFileSync(intentPath(root, slug), 'utf8'));
+        if (fromHeader !== null) {
+            return fromHeader;
+        }
+    }
+    catch {
+        // no intent.md — fall through to the slug rung.
+    }
+    return buildScope(slug);
 }
 // `--body` reads the final-commit body from stdin (the single-quoted heredoc of
 // D34), so the pb-finish skill can compose a proportional close-out message. Returns

package/node_modules/checkride/CHANGELOG.md

@@ -4,8 +4,235 @@ All notable changes to this project are documented here. The format is based on
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.5.2] - 2026-07-19
+
+### Internal
+
+- Split the release workflow into a gated `publish.yaml` (npm publish with
+  provenance, now paused behind a required-reviewer approval on the
+  `npm-publish` GitHub Environment) and a separate `release.yaml` (GitHub
+  Release from the CHANGELOG), matching the fascicle/plumbbob pattern so the
+  npm publish credential and the release-authoring permission never share a
+  job.
+
+## [0.5.1] - 2026-07-19
+
+### Added
+
+- **A GitHub Pages marketing site** under `site/` — a homepage pitching the
+  elevator case for checkride, a docs hub aggregating the existing
+  `docs/*.md` guides into a concise sidebar reference, and a full
+  CLI/config/programmatic API reference — plus the GitHub Actions workflow
+  that deploys it.
+- `docs/why.md` — the case for adopting checkride: what it's selling, the ROI
+  against ad-hoc scripts and task runners, and straight answers to the
+  objections that come up in an adoption conversation.
+
+## [0.5.0] - 2026-07-19
+
+### Contract
+
+- **The `order` field is now a first-class, promised scheduling surface.** A
+  config entry's `order` accepts a **number** — a wave, where distinct wave
+  numbers run in ascending order with a barrier between them, checks sharing a
+  number run concurrently, and decimals sequence steps within a wave (`1` before
+  `1.1`) — or one of `first`, `last`, `middle`, `single`, `any`. It is honored
+  on every object-form entry: a slot's `{ use, order }` and a custom check
+  alike. `first`/`last` keep their exact historical meaning, pinned by a
+  backward-compat contract test. See `docs/contract.md` §"Check ordering and
+  concurrency".
+- **Two deliberate default-placement changes**, both noted in `docs/contract.md`:
+  a config-only custom check with **no** `order` now defaults to `any` (the main
+  group) instead of the old implicit `last` — set `"order": "last"` to restore
+  the previous placement — and a catalogue-filling custom entry's `order`, which
+  earlier releases documented as ignored, is now **honored**. A sequential
+  default run is unaffected in verdicts and summary order; the difference is
+  visible only under concurrency or beside a numbered wave.
+- **New `--concurrency <n>` flag.** Sets the size of the pool that runs a wave's
+  checks concurrently (`1` = sequential; the default is a conservative cap
+  derived from the CPU count). `--bail` overrides it: the run goes fully
+  sequential and a one-line stderr note reports that `--concurrency` was ignored
+  (the combination is safe, just slower — not a usage error). Additive to the
+  flag contract and contract-tested.
+- **`total_duration_ms` is now the run's wall-clock duration.** Under
+  concurrency the summary's total is measured wall-to-wall rather than summed
+  across checks; the two are identical for any sequential run (including
+  `--bail`). The `checks` array stays in deterministic group order — the run's
+  scheduling sequence, never completion order. `schema_version` is unchanged.
+
+### Added
+
+- **A publish-ready bundle of four opt-in slots** that take the definition of
+  done past static publishing lint (`publint`, `attw`) and out to the shipped
+  artifact. Each is a built-in or runs the consumer's own `build`/`tsc`, so
+  enabling them adds **zero devDependencies**:
+  - **`build`** (wave 10) runs the consumer's `build` script, so the artifact
+    checks below inspect fresh output rather than a stale `dist/`. An opted-in
+    `build` on a repo with no build script stands down as a skip, never a red
+    check.
+  - **`pack`** (wave 20) packs the tarball with a dry-run and fails if a required
+    file (a resolved `exports`/`main`/`types`/`bin` target, or `README`) is
+    missing or a forbidden one (`src/`, tests, `.ts` sources — the
+    `dist/**/*.d.ts` declarations excepted) is shipped. npm/pnpm only; yarn/bun
+    report **unavailable** until a per-manager adapter lands, like `security`.
+  - **`smoke`** (wave 20) imports every `exports` entry of the built package
+    through its own resolution map and asserts each declared value export is live
+    at runtime — a liveness check, not a type check.
+  - **`snippets`** (wave 20 / `any`) type-checks the fenced code blocks tagged
+    `<!-- snippet: check -->` in `README.md` and `docs/*.md`. The default
+    `snippets` adapter checks against source; a second `snippets-dist` adapter
+    checks against the built `.d.ts`. A slot opted in with zero tagged fences is
+    a hard error.
+
+  All four are opt-in (`--all`, `--include`, or config), so a default run is
+  byte-for-byte unchanged. They **order themselves**: `build` at wave 10 precedes
+  `pack`/`smoke`/`snippets`/`publint`/`attw` at wave 20, so `checkride --all`
+  builds before it inspects the artifact with no ordering config. `checkride
+  init` on a library can scaffold the bundle.
+
+### Changed
+
+- **A dependency can now activate a slot, not just its config file.** Adapters
+  whose tool runs correctly with zero config — `oxlint` (lint), `knip` (dead),
+  `vitest` (test), `cspell` (spell), and `prettier` (the opt-in format slot) —
+  now also activate when the package appears in `dependencies`/`devDependencies`,
+  as a backup to the detect-file signal. A repo that installed one of these but
+  never wrote its config file gains that check on upgrade; `doctor` names which
+  signal matched. This widens the default run for those slots and is a
+  deliberate, noted behavior change.
+- **Checks now run concurrently within a wave by default.** The orchestrator
+  schedules the wave sequence — `first`s, the numeric line ascending (equal
+  values through a bounded pool, a barrier between distinct values), `single`s
+  exclusively, then `last`s — instead of strictly one-at-a-time cheapest-first.
+  `--bail` keeps the sequential fail-fast path. The catalogue ships ordered so
+  existing default runs produce the same verdicts and the same summary order as
+  before, only faster; `mutation` runs as a `single` (exclusive) because Stryker
+  saturates every core and races the real test run's cache.
+- **`mutation` now ships uncapped (`timeout: 0`) by default.** A real Stryker run
+  legitimately outlives the 600s per-check cap; because `mutation` is opt-in and
+  never part of the definition-of-done gate the cap protects, its adapter runs to
+  completion instead of tripping a timeout under `checkride --all`. Every other
+  slot keeps the safe-by-default cap; override per check or globally with
+  `timeout`.
+
+## [0.4.3] - 2026-07-18
+
+### Internal
+
+- Refactored for maintainability: decomposed high-complexity functions across
+  the orchestrator, `init`, `doctor`, `config`, and the baseline code into small
+  single-purpose helpers, extracted shared option/stanza helpers, and broke
+  internal import cycles. No change to runtime behavior or the public API.
+- Zeroed the project's grandfathered debt: cleared the `lint`, `dead`, `dupes`,
+  and `health` baselines and removed checkride's own `checkride.baseline.json`,
+  so the repo passes a full `pnpm check` with no suppressions.
+- The repo's own default `pnpm check` now also runs the `dupes` and `health`
+  slots. Mutation stays opt-in (`pnpm mutation`): a cold full pass has no warm
+  incremental cache in CI and would time out the gate.
+
+## [0.4.2] - 2026-07-18
+
+### Fixed
+
+- **The `dead` (fallow) slot now actually gates.** checkride ran fallow in JSON
+  mode, which exits `0` even with findings, so the slot reported ✔ while fallow
+  had real issues. checkride now reads fallow's JSON report and derives the
+  verdict from the issue count instead of the (unreliable) exit code — so the
+  slot fails `pnpm check` on new findings and passes only when clean or fully
+  baselined. An **unrecognized fallow report fails loudly** (explicit
+  "unsupported schema_version" / "unrecognized kind") rather than passing
+  silently.
+- **fallow ≥ 3.5 support.** The dead-code parser reads fallow's current
+  `schema_version` 7 JSON (2.x emitted schema 4 with an incompatible layout).
+  The pinned devDependency moves from `fallow@2.48.0` to `fallow@3.5.0`.
+
+### Added
+
+- **`checkride baseline` now grandfathers fallow findings.** A fingerprint
+  extractor keys each fallow finding by kind + file + symbol, so fallow slots
+  participate in `checkride.baseline.json` like `lint`/`struct`/`spell` (and
+  ratchet the same way). Repos that prefer fallow's native `--save-baseline`
+  suppression can still use it — see `docs/tools.md`.
+- **New opt-in `dupes` and `health` slots.** fallow's duplication and
+  complexity analyses are now first-class checks (`--include dupes,health` or
+  `"dupes": "fallow"` in config), each with gating and baselines. They stay
+  opt-in so adopting checkride never fails a repo on duplication/complexity it
+  never signed up for.
+
+## [0.4.1] - 2026-07-11
+
+### Internal
+
+- Docs refresh: updated the reported mutation score to 69% and bumped the README `$schema` example to v0.4.0.
+
+## [0.4.0] - 2026-07-11
+
+### Contract
+
+- **An unknown slot name is now a usage error.** An unrecognized slot in
+  `--only`, `--skip`, or `--include` (e.g. `checkride --only lints`) exits **2**,
+  naming the bad slot and the valid set (catalogue slots plus config
+  custom-check names). It previously matched nothing and exited **0** — a typo
+  could silently disable the gate, the worst vacuous green in a definition-of-done
+  check. See `docs/contract.md` §CLI.
+
+### Added
+
+- New-project `checkride init` refuses to overwrite existing files, listing
+  every collision, and writes nothing; `--force` overrides. Existing-project
+  mode (additive-only) is unchanged.
+- Per-command `--help` (`checkride init --help`, etc.); new-project `init` ends
+  by printing the next command to run; `checkride baseline` now rejects stray
+  flags instead of ignoring them.
+
+### Changed
+
+- `checkride init` scaffolds an exact checkride version (no caret), and the
+  README install uses `pnpm add -D -E checkride`, matching the pre-1.0
+  exact-pin policy consumers are told to follow.
+- Malformed consumer JSON (`.claude/settings.json`, a project `package.json`)
+  now produces an error naming the offending file instead of a bare stack trace.
+
+### Fixed
+
+- **Interrupts no longer orphan checks.** Ctrl-C (SIGINT) or SIGTERM on a
+  running `checkride` is forwarded to every in-flight check and group-kills its
+  whole process tree before exit, then re-raises so the shell still sees the
+  conventional signal exit (130/143). Since checks run in detached process
+  groups (for the timeout kill), a plain interrupt previously left them running.
+- `doctor` distinguishes a version probe that **timed out** from one that
+  **could not be parsed** (30s probe), so a slow `pnpm --version` is no longer
+  misdiagnosed.
+- `checkride init --baseline --dry-run` no longer writes a real
+  `checkride.baseline.json` — a dry run now truly writes nothing.
+- A timed-out check's whole process group is killed (wrapper-spawned
+  grandchildren included), and output is captured with a UTF-8 decoder so a
+  multibyte character split across read chunks survives intact.
+- `checkride fix` runs under the detected package manager (e.g. `npx` under
+  npm), matching the run path instead of assuming pnpm.
+- A slot's stale `.check/` artifacts are cleared before it re-runs, so a leaner
+  or empty run can't leave the previous run's output behind as authoritative.
+
+### Internal
+
+- Docs pass: README restructure linking all six `docs/` files and splitting the
+  existing-repo vs new-project install paths, getting-started/tools sync,
+  reconciliation of the "locked by `test/contract/`" claim with real tests, and
+  a batch of drift corrections.
+- Release automation: tag↔version guard on release, CI concurrency group,
+  security-only Dependabot; `publint` and `attw` added as dev checks and
+  dogfooded; explicit test timeouts for slow-spawn machines; npm publishing
+  switched to Trusted Publishing (OIDC).
+
 ## [0.3.0] - 2026-07-10
 
+### Contract
+
+- Three additions to the promised surfaces, each recorded in `docs/contract.md`
+  and locked by `test/contract/`: the `summary.json` `checks_run` field, the
+  `--strict` flag, and the `DEFAULT_TIMEOUT_SECONDS` export. (Heading added
+  retroactively — the full entries are under **Added** below.)
+
 ### Added
 
 - **Vacuous-green signal.** `summary.json` gains a top-level `checks_run` count
@@ -238,6 +465,13 @@ The first real release. (`0.0.0` was a name-claim placeholder.)
 - Flags: `--only`, `--skip`, `--bail`, `--json`, `--changed`, `--all`,
   `--include`.
 
+[0.5.2]: https://www.npmjs.com/package/checkride/v/0.5.2
+[0.5.1]: https://www.npmjs.com/package/checkride/v/0.5.1
+[0.5.0]: https://www.npmjs.com/package/checkride/v/0.5.0
+[0.4.3]: https://www.npmjs.com/package/checkride/v/0.4.3
+[0.4.2]: https://www.npmjs.com/package/checkride/v/0.4.2
+[0.4.1]: https://www.npmjs.com/package/checkride/v/0.4.1
+[0.4.0]: https://www.npmjs.com/package/checkride/v/0.4.0
 [0.3.0]: https://www.npmjs.com/package/checkride/v/0.3.0
 [0.2.1]: https://www.npmjs.com/package/checkride/v/0.2.1
 [0.2.0]: https://www.npmjs.com/package/checkride/v/0.2.0