CIC · orchestration harness
Harness
The CIC orchestration harness (tools/cic-harness, phases 0–6) as its
own evidence describes it. Two records, kept apart on purpose: the harness README says what was
applied, and a real node --test run says what passes now. Every
number below says which of the two it came from and when that was established.
This page is a read-only view: it cannot run the suite, re-run it, or mark a
phase green.
The suite, last run
Phases
“Record says” is the README’s claim, with its date and agent. “Suite says” is the run above, attributed by the test files the README names for the phase. A phase with no test file has no automated coverage here, whatever the record says.
Skipped, by name and reason
A skipped test is neither a pass nor a fail. It is a gap the suite admits to.
What is not covered
From the README’s own “Known API gaps” and “Honest limits” sections, verbatim after Markdown is stripped.
Other tests in the same suite
Files no phase names. Listed so the total above reconciles and nobody reads “157 tests” as “157 harness tests”.