Drop the machine-coverage check; the framework runs it now #49

Merged

vnprc merged 1 commit from agent/drop-machine-coverage into master

2026-10-22 00:41:47 +01:00

allod-agent commented

2026-10-22 00:35:11 +01:00

Member

Nothing changes on any running machine. The template drops its copy of the machine-coverage check, because the same check now lives in the framework (allod/archetypes#148) and runs in every deployment's gate against that deployment's own data, which the copy here never could: a deployment builds from a private fork of this repo, and the fork never took the template's checks. Under the deletion rule a check goes when a cheaper witness pins the same property. What stays identical: every data file, every lib output, the other nine checks. Proof: the gate on this branch is All 10 steps passed (checks: 9 built) and nothing in the tree references the check. Merge order: after the archetypes pull request has landed, so no gate is ever without the check. If it is wrong, revert the one commit and the template copy is back.

Closes allod/archetypes#148

Risk

R0. Deletes a check and its two references; no data, output or runtime behavior changes.

Validation

allod check . on the branch: All 10 steps passed (checks: 9 built), no step named machine-coverage.
git diff --stat HEAD~1: exactly README.md, checks/default.nix, checks/machine-coverage.nix.
grep -rn machine-coverage README.md checks/ finds nothing.

Nothing changes on any running machine. The template drops its copy of the `machine-coverage` check, because the same check now lives in the framework (allod/archetypes#148) and runs in every deployment's gate against that deployment's own data, which the copy here never could: a deployment builds from a private fork of this repo, and the fork never took the template's checks. Under the deletion rule a check goes when a cheaper witness pins the same property. What stays identical: every data file, every `lib` output, the other nine checks. Proof: the gate on this branch is `All 10 steps passed (checks: 9 built)` and nothing in the tree references the check. Merge order: after the archetypes pull request has landed, so no gate is ever without the check. If it is wrong, revert the one commit and the template copy is back. Closes allod/archetypes#148 ## Risk R0. Deletes a check and its two references; no data, output or runtime behavior changes. ## Validation - `allod check .` on the branch: `All 10 steps passed (checks: 9 built)`, no step named `machine-coverage`. - `git diff --stat HEAD~1`: exactly `README.md`, `checks/default.nix`, `checks/machine-coverage.nix`. - `grep -rn machine-coverage README.md checks/` finds nothing.

allod-agent added 1 commit

2026-10-22 00:35:11 +01:00

Drop the machine-coverage check from the template 886e1124bf

The check now lives in allod/archetypes, which runs it against every
deployment's own inventory, host-key table and identities through the
follows redirects its deploy flake already applies. A copy here under
the deletion rule in testing.md only ever protected the public
template, not the private fork any deployment actually builds, so the
framework copy is the cheaper standing witness.

Refs allod/archetypes#148