docs(register): v1.12.0 deployed — evidence for C-331, C-347, C-348

[Polichinel]

Docs only. Records what the v1.12.0 redeploy measured, not what it was assumed to have achieved.

The redeploy ran all three server_quickref.md steps — tag file, git fetch && git checkout, uv sync — which is C-343's entire content.

tag file	v1.11.0 → v1.12.0
HEAD	79fc47a → b480a80 (tag: v1.12.0)
package	1.11.0 → 1.12.0
interpreter / raster	3.12.3 · tifffile 2026.5.15 · imagecodecs 2026.5.10 — unchanged, as the release predicted for a ≥3.12 host

C-331 — already resolved, now actually running

#423 fixed it and drilled it with a canary. A fix merged is not a fix running: the deployed tag carried the old form until today. Both halves checked on the host — all three sites read printf 'url = "%s"' … | curl -K -, and then curl -K - was executed on the box.

The second check is the one that mattered. Every ping is guarded by || true, so a form this machine's curl rejected would have silenced the dead-man switch while looking identical to a working one. That is the C-322/C-324 distinction, applied before anyone had to learn it again.

C-348 — measured, and deliberately left open

The host runs Python 3.12.3, resolving the current raster fork. Production has been on the right side of the floor throughout.

Read the reason rather than the result: 3.12.3 is Ubuntu 24.04's system interpreter, and the guide in force said "Install Python 3.10+". The server is correct by distro accident, not by decision — which is exactly what the entry says, so measuring it does not close it. One observation is not an assertion, and the next reprovision on a distro shipping 3.11 would silently install the March-2026 decoder.

C-347 — trigger fired and actioned

test-py313 reported green on development and on main, then was added to the required-status-check lists on both, with the result read back rather than assumed — C-340's discipline applied to branch protection rather than merge methods.

This pull request is the first to pass through the new required check, which is the only way to learn that requiring it does not deadlock every merge.

C-343 — instance clean, concern open

Tag file, HEAD and environment all agreed before the deploy. On 2026-08-08 those three disagreed for five days. The instance is remediated; the concern is not, because #434 — the pre-flight that would prevent recurrence — was closed unstarted with epic #421. Said plainly so a clean reading does not imply a fix.

Verification

Counts unchanged: 349 IDs / 42 open / tier sum 42, header 1960 ≤ 3500. Nothing opened or closed, which is correct. All register, changelog and citation guards pass; validate_docs.sh PASSED; ruff clean.

Reviewed at one round rather than the full ritual — docs-only, and no data can be silently wrong. That is the #421 close-out rule applied rather than quoted.

🤖 Generated with Claude Code