@blueforge-studio/test-resume

Runner-agnostic crash-safe resume for test runs. No Playwright or vitest imports, no dependencies beyond node:.

• Ledger: append-only JSONL, last record per unit wins, torn trailing line ignored, started records so a unit with no result after a crash reads as interrupted.
• Fingerprint: run-level key (fingerprintOf), per-unit input hash (hashFile), optional coarse gitKey.
• Planner: planUnits({ listing, state, failedOnly, hashOf }) returns what to run, carry or discard.
• Classifier: classifyOutcome separates a failing test from a run cut out from under it (vanished cwd, EIO, signal kill).
• Exit codes: exitCodeFor returns 0 passed, 1 failed, 75 interrupted or not run (rerun to resume), 130 signal.

A unit is whatever the runner schedules: a test, a spec file, a package. Keys are opaque strings.

Status file and app-dev-db

• snapshotStatus + writeStatusFile: a live status.json (state, counts, running units, remaining) derived from the ledger and written tmp+rename, for dashboards and humans to poll.
• testRunReading: turns a finished run into test.run flags for scripts/push-devdb-reading.mjs (app-dev-db producer contract v0.5). An interrupted run, or one with unrun units, returns push: false: a reading is a finished measurement, and the resumed run pushes the complete one. No HTTP here; the producer script owns the envelope, retries and secrets.