release: forjar 1.31.0 — the cut (PMAT-574, closes #574) by noahgift · Pull Request #575 · paiml/forjar

noahgift · 2026-09-16T04:45:54Z

What this is

The 1.31.0 cut: version, lock, the CHANGELOG heading over the window, the crux comparison each behaviour owes, and the ledger bookkeeping gate B measures.

paiml/infra is blocked on this release — PMAT-607 folds machines/{yoga,gx10}/forjar-ephemeral.yaml into the host manifest and its done-when is a drift verdict 1.30.0 cannot give (paiml/infra#605).

What ships

PR	ticket	behaviour
#563	PMAT-562	`forjar drift` exits 1 on any DRIFTED line, on every run, with no flag
#569	PMAT-564	`forjar drift` declines — exit 2, the count named — when it inspected none of the resources it was asked about, and never grades a resource from a manifest it was not given
#568	PMAT-560	a `service` is converged only while the loaded unit executes the declared program (`exec_start` / `exec_sha256`)

Gates, measured on this branch

GATE H PASS 3 of 3 behaviour bullet(s) under [1.31.0] reconciled in docs/audits/crux-1.31.0.md, each naming >= 3 of the 28 surveyed systems
GATE T PASS 8 tagged release(s) since v1.25.0 reconcile with git and GitHub and 53 ticket(s) carry their tag and say they shipped; 5 ticket(s) from 5 PR(s) merged since v1.30.0 carry release:v1.31.0; cut in flight: Cargo.toml is at 1.31.0
Ratchet arm 7, RED first: CB-2112 37/35, CB-2114 36/34, CB-2115 49/43 → repaired to 34/35, 34/34, 43/43. Nothing lowered.

What is deliberately not here

PMAT-565 (#570, the per-machine lock names its writer) was still open at the cut, so it owes no crux row and its ticket carries release: 1.32.0.

🤖 Generated with Claude Code

Version, lock, the CHANGELOG heading over the three-PR window, and the crux comparison each behaviour owes. The window is paiml/infra#605 answered end to end: drift's verdict reaches the exit code (PMAT-562, #563), a run that inspected none of the resources it was asked about declines instead of reporting zero drift (PMAT-564, #569), and a service is converged only while the loaded unit executes the declared program (PMAT-560, #568). GATE H PASS 3 of 3 behaviour bullet(s) under [1.31.0] reconciled in docs/audits/crux-1.31.0.md, each naming >= 3 of the 28 surveyed systems. The rows carry no backticks inside the key span, because the gate greps the bullet's first six words LITERALLY and `forjar drift` does not contain "forjar drift". The bookkeeping gate B measures is part of the cut, not around it. Arm 7 was RED on this branch: CB-2112 37 against 35, CB-2114 36 against 34, CB-2115 49 against 43. Repaired rather than raised, by the baseline's own convention (a row whose id tail is the issue number, a milestone, and a bare `release:`): PMAT-557 #557, PMAT-560 #560, PMAT-564 #564 -> status completed; their issues are closed, so the open rows read as ORPHAN-ROADMAP and ISSUE-CLOSED both PMAT-560, PMAT-574 -> release: 1.31.0 #565 #572 #573 -> rows minted under their issue numbers, release: 1.32.0, milestone 1.32.0 PMAT-559 -> its row's title was truncated when it was minted, which is what the DRIFT finding was Measured after, on this tree: CB-2112 34 (ceiling 35), CB-2114 34 (34), CB-2115 43 (43). Nothing is lowered here — a ceiling may only be lowered from a measurement of the COMMITTED tree. PMAT-574 stays inprogress: a ticket is open in its own PR and the booking PR marks it completed, which is the rule the commit-msg hook enforced when this commit first said completed. PMAT-565 is NOT in this release: #570 was still open when the cut was made, so its behaviour owes no crux row and its ticket carries release: 1.32.0. Pmat-Ticket: PMAT-574 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…ersion lines (Refs PMAT-574) `make dogfood-release` exited 0 on the committed tree at 9e3a474 with all nine gates green: GATE A PASS 5 of 5 merged PR(s) since v1.30.0 carry a harness receipt GATE B PASS ... CB-2112=34/35 CB-2114=34/34 CB-2115=42/43 held GATE C PASS 211 CLI name(s), 12 MCP tool(s), 12 HTTP verb(s) GATE D PASS 18 documented invocation(s); version claims reconcile with Cargo.toml GATE E PASS 5 of 5 merged PR(s) since v1.30.0 carry a quorum receipt GATE F PASS line coverage 96.43% >= 95%; nothing to mutate (no .rs differs) GATE G PASS 43 contract(s) validate GATE H PASS 3 of 3 behaviour bullet(s) reconciled in docs/audits/crux-1.31.0.md GATE T PASS ... cut in flight: Cargo.toml is at 1.31.0 The three reds cleared BEFORE that run are in docs/audits/logs/PMAT-574-cut.log with the measurement either side, because a gate that was never red proves nothing about itself. The README's two version lines move 1.30 -> 1.31. Gate D passed either way — Cargo reads `forjar = "1.30"` as `>=1.30.0, <2.0.0`, which admits what this cut ships — so this is the cut keeping the documented version equal to the shipped one, not a gate forcing it. The first draft of the receipt claimed the lines were already correct; they were not, and the claim is replaced by what the file says. Pmat-Ticket: PMAT-574 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

noahgift · 2026-09-16T05:28:45Z