Replace the stopgap check.sh with allod check #7

Merged

vnprc merged 1 commit from agent/allod-check-gate into master

2026-09-28 14:58:56 +01:00

allod-agent commented

2026-09-28 03:33:15 +01:00

Member

Owner summary

Merge this one last. It closes allod/tools#239. The allod/archetypes PR from the same series goes first.
What changes on a running machine: nothing. No machine builds or runs the files touched here.
What changes for whoever checks this repository or a fork of it: the stopgap ./check.sh is gone. The command is allod check, from allod/tools, and it can run the whole gate against an unmerged branch of a data repository.
A machine needs tools that carry the command. Until the allod/tools pin is bumped and a machine is rebuilt, allod check is not installed there.
What stays identical: the steps that run: the same 6, with 1 check built. flake.nix, flake.lock and tests/ are untouched.
If it is wrong: revert this PR; the stopgap comes back.

Closes allod/tools#239

What changed

44 lines removed, 10 added: check.sh deleted, and the README's Check section rewritten around allod check, with allod check --override-input <input> <worktree> as the way to prove a branch before it merges.

Risk

R1. Documentation and the removal of a script nothing else calls.

Left alone: the README's section on the composed-layer canary still says "nix flake check runs it". That is true, and outside the section this change is about.

Validation

Run by the integrator on 2c5d74b, with allod built from allod/tools at 745c78b:

Command	Result
`allod check`	exit 0, "All 6 steps passed (checks: 1 built)", 31 s
`allod check --override-input inventory <inventory checkout>`	exit 0, 6 steps, 1 check built, 31 s; the run names the override; `flake.lock` unchanged
`grep -rn 'check\.sh' .`	no output

Not run: the gate on a deployment fork with a real fleet.

No review pass: R1.

## Owner summary - **Merge this one last.** It closes allod/tools#239. The `allod/archetypes` PR from the same series goes first. - **What changes on a running machine:** nothing. No machine builds or runs the files touched here. - **What changes for whoever checks this repository or a fork of it:** the stopgap `./check.sh` is gone. The command is `allod check`, from `allod/tools`, and it can run the whole gate against an unmerged branch of a data repository. - **A machine needs tools that carry the command.** Until the `allod/tools` pin is bumped and a machine is rebuilt, `allod check` is not installed there. - **What stays identical:** the steps that run: the same 6, with 1 check built. `flake.nix`, `flake.lock` and `tests/` are untouched. - **If it is wrong:** revert this PR; the stopgap comes back. Closes allod/tools#239 ## What changed 44 lines removed, 10 added: `check.sh` deleted, and the README's Check section rewritten around `allod check`, with `allod check --override-input <input> <worktree>` as the way to prove a branch before it merges. ## Risk R1. Documentation and the removal of a script nothing else calls. Left alone: the README's section on the composed-layer canary still says "`nix flake check` runs it". That is true, and outside the section this change is about. ## Validation Run by the integrator on `2c5d74b`, with `allod` built from `allod/tools` at `745c78b`: | Command | Result | | --- | --- | | `allod check` | exit 0, "All 6 steps passed (checks: 1 built)", 31 s | | `allod check --override-input inventory <inventory checkout>` | exit 0, 6 steps, 1 check built, 31 s; the run names the override; `flake.lock` unchanged | | `grep -rn 'check\.sh' .` | no output | Not run: the gate on a deployment fork with a real fleet. No review pass: R1.

allod-agent added 1 commit

2026-09-28 03:33:16 +01:00

Delete the stopgap check.sh for the tools command 2c5d74b13e

`allod check` in allod/tools does what this script did, and reaches the
machine with the other workspace tools, so the stopgap that shelled out to
the pinned archetypes revision's gate goes.

The README's Check section names the command and gives
`allod check --override-input <input> <worktree>` as the way to run the
whole gate against a data-repo branch before it merges, in place of forcing
checks one at a time. No `allod-check.toml` here: the only passive output is
`vmFacts`, which is built into the command.

Refs allod/tools#239