$ Sreditor · Build Plan

Built across one extended session, in seven phases plus a corroborating-signals extension, each shipped through Sreditor’s own required propose → implement → verify → archive loop: init, judge (with drift-auditing and corroborating signals), rollup (with a real pre-call cost estimate), report (T661-line-structured markdown), plus scan, status, and doctor.

npm publish and tagging v0.1.0 is the one remaining step before the tool is installable by anyone other than Robin — held back pending sign-off, not a technical blocker.

The adapter interface that reads a project’s change history is already designed to be tool-agnostic, but OpenSpec is the only source format actually built. PDF/CSV report output is the other named gap — markdown-only today.