runtime/trace.ts (exported by runtime/mod.ts as trace) MUST read what the kernel judges: the specifications of a folder (specs/NNN-slug/spec.md and reviewed.tsv), the .ts files under roots (leaving out node_modules), as paths relative to the repository with /; and MUST hold findings against a baseline file (holdBaseline): read it (a missing file is an empty baseline), judge, and give the lines of FR-003 and an exit status (0 when nothing is new or stale, 1 otherwise), or, with write, write the baseline from the findings and give 0. It MUST print nothing itself: the harness's tool prints the lines. Every path it gives is relative to the repository and /-separated on every system, Windows included, so a ladder's homes and a baseline's keys match the same files everywhere.
Enforced (check): .github: cd commons/data && bun test suite/ — runtime/trace.test.ts: a fixture tree on disk read; its findings held against a baseline written, passing, then failing when stale
Proved by: mizan/suite/host-trace.test.ts
Tests: passed: suite/host-trace.test.ts a tree read, its findings held against a baseline that only shrinks; passed: suite/host-trace.test.ts every path is relative and /-separated on every system, Windows included
Cited by: host/trace, Mizan