[junixlabs]

INV-027 and INV-028 land in the one artifact a reader looks at first. Server-side, as
everything on that page is.

Why — a Flow's Intents, each with its frozen record, labelled provenance, never
truth so nobody reads the citation as a verification of the sentence. A Flow with no
Intent says so rather than rendering an empty list.

Outcomes now draw three states, not two:

	Drawn as
checked, and the check holds	● checked with the assertion id
a check is declared, nobody has run it	dashed never checked
no check declared	dashed no check declared
the check refutes it	REFUTED in error colour

Collapsing any of those into "fine" would be the silent boundary INV-025 forbids, in the
place it would do the most damage.

A weak test, caught and fixed

The first version asserted the "no check declared" state against traceos-itself, where
every outcome now has a check — so the assertion could not fail for the case it was
named after. Repointed at examples/ecommerce, which has purchase.rejected with no
check, and verified it fails when the branch is broken. Same for the Intent rendering.

Checks

39/39 groups, 185/185 assertions (three new). check_docs 28/28, check_locators
38/38, ratchet exit 0 — discharged by re-reading explore.build and confirming the
browser still computes nothing: the JS looks up a precomputed IMPACT table and toggles
hidden, and the new Intent and Outcome rendering is Python.