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

controller/internal/stacks/updateorder.go

@@ -95,7 +95,11 @@ func CatalogOrder(s Stack) UpdateOrder {
 //   - two references to DIFFERENT images (`alpine:3.20` against `…/bookstack:26.05.2`) — the numbers
 //     are comparable and the comparison is meaningless, which is the worst kind of false positive;
 //   - any tag that is not plain digits and dots: `16-alpine`, `latest`, `26.05.2-ls310`, `stable`,
-//     a date stamp, a git sha. 23 of the catalog's 66 pins float exactly like this (§8.1).
+//     a date stamp, a git sha. **10 of the catalog's 66 pins float like this**, RECOUNTED
+//     2026-09-21 — 6 two-part lines (mariadb:11.4/11.6/12.3, claper:2.5, opengist:1.13,
+//     wger/server:2.6) and 4 major lines (postgres:15/16-alpine, redis:7-alpine,
+//     postgis:16-3.5-alpine). The "23" this comment used to carry matched no definition the
+//     catalog supports today; see 09 §8.1.
 //
 // THE ORDER ITSELF IS util.Version.Compare AND NOTHING ELSE. The house rule is one comparator in
 // this repo; this function is a tag NORMALISER in front of it, never a second implementation.