ops: fleet floor raised to 0.255.0 — and it delivered on its own

POST /configuration/global-floor with min_controller_version=0.255.0 and the
declared min_agent=0.131.0 (R-472); 303 flash=floor_set, read back from the
form, not from the POST.

The proof is the N100: it was never hand-deployed and its own Docker reports
felhom-controller:0.255.0 healthy within five minutes of the save. Three boxes
remain below — all BLOCKED or DOWN, which is a floor being held, not a floor
failing; each takes it on its next check-in.

R-580 filed: curl's %{redirect_url} rebuilds the request URL WITH the --netrc
credentials in it, so the hub password was printed into the session's own
output. Nothing written to a file, nothing committed. The build-deploy skill
now carries the rule.

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

skills/felhom-build-deploy/SKILL.md

@@ -130,6 +130,11 @@ curl -fsSL -o /tmp/rt.iso https://iso.felhom.eu/felhom-installer-<VER>-pve<PVE>.
   dashed focus ring, and `Enter` lands in text *fields*, not `Next`. Not checking once aborted an install.
 - **Proof installs register unclaimed appliances at the hub — discard them** or R-131 grows:
   `curl -u ":$HUB_PW" -X POST http://<hub-clusterIP>:8080/appliances/<id>/discard` → 303.
+
+> **Never pair `-w '%{redirect_url}'` with `-u` or `--netrc` (R-580).** curl rebuilds the request URL
+> for that variable **with the credentials in it**, so the hub password is printed even though it
+> never appeared in the command. `%{url_effective}` and `%{referer}` do the same. Print
+> `%{http_code}` alone; read the destination from `-D-` headers if you need it.
   The verb is **`/discard`**, POST only (`hub/internal/web/server.go:345`); `/delete` 404s.
 - Venue: `demo-hp`, scratch `dir` storage at **`/mnt/nvme-1tb` root** (a subdirectory reads
   `disconnected` forever — the agent's `exactMount` check). Never `local-lvm`. Remove the storage at teardown.