evening: rules file in place; R-483 CLOSED (catalog, operator-confirmed); R-479 CLOSED (controller v0.241.0, proven live); R-481 blocked on the one-host-one-customer model; R-491 filed

STATUS.md

@@ -1,5 +1,34 @@
 # STATUS — what works, what's broken, what's next
 
+**Updated 2026-09-13 (evening, before the night) — your four items.**
+
+**Decisions I took.** (1) The rules file now sits in the workspace root and all three repos,
+byte-identical; the gate that checks instruction files required three lines at its top saying it
+loads in every session on purpose, so all four copies carry them. (2) The photo fix was applied to
+your own test instance on the HP through the Update button, not by hand, and I added one test
+account with one photo there.
+
+**What I did.** The rules file: done. The photo problem: the app's backend serves photos itself,
+through a small web server inside its own image; our template sent every request to the front page
+server, which has no photos. Fixed in two cuts — the second one because the first spoke to the wrong
+port and got empty pictures. Proven without a browser: a photo now comes back as a real image
+through the public address, and you confirmed it in your browser at 21:49. The tier-order
+ruling: built as controller 0.241.0 — an app whose data lives in mounted folders now prefers the
+remote copy over its own-drive copy, and the hold message ends with what the chosen copy holds.
+Live on both machines (0.241.0, delivered by the floor in 16 and 18 seconds) and proven on the HP
+with a throwaway Nextcloud.
+
+**What broke on the way.** Nothing standing. One new finding: after an app is removed, its
+"held after a failed update" mark stays behind, so a reinstall would start blocked. Cleared by hand,
+filed (R-491) for the next release. Register: 206 open / 191 closed.
+
+**Needs you.** The scratch guest: the ruling as written cannot be built — the hub ties one box to
+one customer, and a second enrolled customer on the HP would replace the HP's own enrolment. Two
+options: a second guest under the HP's own customer (reversible, tonight-ready, but its reports
+would clash with the HP's page unless it stays unenrolled), or a nested appliance VM enrolled as its
+own box (fully enrolled, hours to build). My pick: the first, unenrolled. **If you do nothing:**
+tonight's rotation keeps restoring in place and skips the standing nine.
+
 **Updated 2026-09-14 (the night of 13→14 — "be a customer for the night", first run). Written in
 the order the rules ask for.**