Correct a stale count repeated in four places: 10 floating pins, not 23

Recounted at catalog 18a6d2d8: 66 unique pins — 48 full X.Y.Z, 6 two-part
lines, 4 major lines (10 float), 8 exact versions wearing a variant suffix.
The '23' carried since v0.233.0 matches no definition the catalog supports.
Definition written down beside the number so it can be rechecked.

Also: CONTEXT said the fleet floor was 0.257.0; the hub says 0.259.0.

Comment and doc only — no behaviour change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

REPORT.md

@@ -82,10 +82,18 @@ Image `gitea.dooplex.hu/admin/felhom-controller:0.260.0` built and pushed. **Dep
 three guests**: demo-felhom 9201, demo-hp 9201, and demo-hp 9202 (the scratch guest, upgraded from
 0.245.0 for the live proof).
 
-**The fleet floor was NOT raised — that is the operator's step**, as it was left for v0.258.0 and
-v0.259.0; it still stands at 0.257.0. Stated rather than silently skipped: the standing rule asks for
-the floor to be raised to deliver a release, and this session deliberately did not, because the two
-preceding sessions recorded floor raises as the operator's own act.
+**The fleet floor was NOT raised, and the number in the repo's own CONTEXT was stale.** CONTEXT.md
+said the floor stood at 0.257.0; **the hub says 0.259.0** (read live from `/configs`, not from a
+document — the operator raised it after that entry was written, which `felhom.eu/STATUS.md` records).
+v0.260.0 therefore reaches the two demo boxes by hand and **no further**.
+
+Stated rather than silently skipped: the standing rule asks for the floor to be raised to deliver a
+release, and this session deliberately did not. **Why:** a floor raise reaches `peti-felhom`, a real
+customer box, and the unprompted-work fence puts anything that changes risk to customer data behind
+an operator word. The two preceding sessions recorded the raise as the operator's own act, and the
+one that happened came after the operator asked for it. Put to the operator with what happens if they
+do nothing: the fix stays on the two demo boxes and the rest of the fleet keeps offering a downgrade
+as an update — which is a badge and a button, not data at risk, so waiting costs little.
 
 Live proof, drift numbers and the state of the whole arc:
 `felhom.eu/documentation/audits/UPDATE-ARC-STATE-2026-09-21.md` and `audits/update-arc-2026-09-21/`.