doxa-maps/internal/fixtures/on-demand-checks.json
Doxa Maps b142fe1178 Two more gates join gates:pre honestly: dxlife walks only the clones, and the calendar stays on demand
check:dxlife walked the whole root-dx-life umbrella, so git worktrees of doxa-life (wt-rg-*) and
a dangling one (research-map-clean, whose .git points at a path that no longer exists) read as
+4,524 "added" files and held it red while the clones were untouched. It now skips any directory
whose .git is a FILE beginning `gitdir:` (keyed on that file, not on `git worktree list`, which
cannot see the dangling one) and .cache with the other generated dirs, and compares the baseline
only within that scope. Result against the 2026-09-20 baseline: 2,844 clone files, +0 -0 ~0. So the
law has held since that date, and the baseline stays as it is: re-taking it would reset the evidence.
Nothing is deleted; research-map-clean may hold the only copy of its work. With no clone on the
machine it reports NOT MEASURED (75) instead of exit 2, so chaining it cannot fail other machines.

check:coverage-consistent fails when the oldest verified link is over 45 days old: its verdict
depends on the calendar, and chained it would turn gates:pre red on 2026-11-08 with no change
(regions measured the margin). Every other clause depends on code and data and is worth running
on every landing, so gates:pre runs check:coverage-consistent:chained (the age knob set out of
reach). The plain script is declared on demand as the freshness run, with that reason. Its poison
self-test still proves every clause can fail.

gates:pre 94/0/2 of 96. The orphan baseline shrinks to 105; 7 checks are declared on demand.
2026-09-29 11:56:47 +00:00

12 lines
1.7 KiB
JSON

{
"about": "check/verify/smoke scripts that must run BY HAND, each with the reason no chain runs it. Being listed here is a decision someone wrote down; check:no-orphan-gates fails on an entry with no reason or no script.",
"checks": {
"check:settled": "asserts the tree is QUIET (no builder running, no recent churn), so it fails inside any build by design: it passed twice standalone, was chained on that evidence, and failed the very next build (2026-09-24)",
"check:catalog-currency": "reads the PUBLISHED tree and needs DOXA_PUBLISHED_BASE; without it it reports NOT MEASURED (75), never a pass",
"check:published": "fetches the live published host (needs DOXA_PUBLISHED_BASE): a property of the deployment, not of this tree",
"check:composite": "rebuilds every bundle with vite to compare its bytes, minutes long by design; on every landing the precondition's fresh step rebuilds the composites that landing reaches",
"check:hardcoded-english": "report-only while its findings are triaged (97 user-visible English strings on 2026-09-29); chaining it now would hold every gate red. Its :self-test IS chained, so the matcher stays proven",
"check:shot-fonts": "checks that the MACHINE taking README screenshots can render emoji (fc-list): a property of that box, not of the product, so it runs before a screenshot session, not in the gates",
"check:coverage-consistent": "the full run includes clause L, the age of the oldest link verification (45 days), which depends on the CALENDAR: chained, it would turn gates red on a date (first 2026-11-08) with no code change. Run it with the link re-verification; every other clause runs in gates:pre as check:coverage-consistent:chained"
}
}