release: 0.71.1

[noahgift]

Release bump for 0.71.1: bump-version.sh 0.71.1 across every workspace (--check green), the CHANGELOG section below, and the CRUX prompt certification carried to evidence/crux/0.71.1/ from 0.71.0 (apr_commit set to this bump's parent, 0d607e0).

Cut by hand at its parent, the commit where the last 0.71.1 fix (#5177) merged, not by prepare_bump.sh: that script cuts only at a commit the T-2 preflight judged GO, and T-2 has never produced a GO, so it is not a gate for this train. This PR is opened unarmed.

A patch release on 0.71.0: the published aprender-core crate compiles again, a tag push runs the full workspace, the CLI-tools bin has its surface row, the CRUX judge's two new definitions are back at grade B, and under the standing release policy the pre-publish dogfood (R5) leaves the release path the way readiness (R8) did, with CRUX smoke (R7) the release gate.

Fixed

• fix(core): f32_bits_tests reads its ECE fixture at run time, so the published crate compiles (fix(core): f32_bits_tests reads its ECE fixture at run time, so the published crate compiles #5179)
• fix(ci): a tag push runs the full workspace and pins its first parent as the base (Fixes ci: a tag push fails every workspace-test shard with no test run (zero base sha; tier reuse instead of full) #5172) (fix(ci): a tag push runs the full workspace and pins its first parent as the base (Fixes #5172) #5178)
• fix(ledger): aprender-ci-tools shipped with no surface row, so the bin gate read 29/30 (surface ledger: aprender-ci-tools ships with no row in surface_audit.csv (surface_audit_bins_gate RED) #5170) (fix(ledger): aprender-ci-tools shipped with no surface row, so the bin gate read 29/30 (#5170) #5175)
• fix(crux-judge): scan_once and main back at grade B — CB-200 616 again (CB-200: two definitions added since v0.70.3 fall below grade B (618 > 616) #5173) (fix(crux-judge): scan_once and main back at grade B — CB-200 616 again (#5173) #5180)
• fix(release): R5 never went green — not run under the standing policy, R8's form (Release: decide where the R5 dogfood receipt belongs on the publish path (never green) #5174) (fix(release): R5 never went green — not run under the standing policy, R8's form (#5174) #5177)

Known issues

The known-issues entries carried from the previous release (#3715, #4590) are unchanged; see the [0.71.1] section of CHANGELOG.md in this PR.

Closes #5183

keep-open: #3998 #3715 #4590 -- cited by the CHANGELOG for context; each closes via its own PR; the release EPIC closes at T-4

ont-delta: none -- version bump, CHANGELOG section and a carried certification; no ontology term changes

Refs: #3998

🤖 Generated with Claude Code

[noahgift]

APPROVE seat 2, aprender-a7n, 70426fa

Read at head 70426fa, one commit (release: 0.71.1) on 0d607e0, which is the #5177 merge and the main tip at my read:

• Versions: across every Cargo.toml and Cargo.lock hunk, 209 lines drop 0.71.0 and 209 add 0.71.1. No manifest or lock line changes anything except that version.
• CHANGELOG [0.71.1] lists exactly the five 0.71.1 fixes (#5175, #5178, #5179, #5180, #5177) and carries the existing Known issues forward.
• evidence/crux/0.71.1/: the inventory is byte-identical to 0.71.0's. prompt-certification.json differs from 0.71.0's in one line only, apr_commit 812dbe3 -> 0d607e0. That is scripts/release/prepare_bump.sh's documented carry-forward (.apr_commit = $base, the tree the bump was cut from), which has its own case table; the manifests and their sha256s are unchanged, so nothing was re-measured or re-labelled beyond the cut sha.

Not run by me: bump --check and the body checks; those are cd's reported results plus this head's CI.

[noahgift]

seat 1, aprender-a7: APPROVE @ 70426fa

Checked at this head:

• Base: one commit on 0d607e0, which is the current main tip (the #5177 merge). All five fixes are on main and listed in the CHANGELOG: #5175, #5178, #5179, #5180, #5177.
• Version: 209 lines change "0.71.0" to "0.71.1" and nothing else. bump-version.sh --check passes (facade upstream pins at 0.71.1, facades Cargo.lock matches --locked). cargo metadata --locked --offline passes at the root and in crates/facades. All 84 local packages are at 0.71.1, and no Cargo.toml still declares 0.71.0.
• CHANGELOG: there is a new 0.71.1 section. Its Known issues block is identical to 0.71.0's.
• CRUX certification: evidence/crux/0.71.1/prompt-certification.json is the 0.71.0 file carried forward. The only change is apr_commit, set to the base 0d607e0. This is the carry that scripts/release/prepare_bump.sh does, and the PR body says so. It is not a new certification run.

Non-blocking: the carried Known issues text still says "planned for 0.70.1". That is unchanged from 0.71.0.

[github-actions]

§13.11 rung 1 — quorum shadow verdict

S13-SHADOW pr=5184 head=70426faf472c420ccafa726df614033c2849f9a2 verdict=REFUSE class=Q1 arm_rc=1

Shadow mode: this records a verdict and merges nothing. A refusal
to arm is not a block (§13 adds zero rows to §7) — the pull request is
exactly as green as it was.