ISO 1.28.0 PUBLISHED on the operator's yes; download page and R-535 updated
gates / gates (push) Successful in 20s
gates / gates (push) Successful in 20s
Uploaded with env-only credentials and verified by ROUND TRIP: the downloaded bytes checksum to a4cd9b6d…, identical to the built file, and the checksum file is served. 1.27.1 stays in the bucket; nothing was overwritten. The download page now names 1.28.0 with the published checksum (BOM preserved, site gates green). R-535 closes with an honest caveat: the new banner ships byte-identical to repo HEAD and the string is in the published payload, but it was never seen on a screen — the box bound itself while the walk was headless. Also corrected: the 1.27.1 heading still said NOT PUBLISHED although it went out on the big night. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
## ISO v1.28.0 — the console stops showing the pairing code once the box is connected (2026-09-16, R-535) — NOT PUBLISHED
|
||||
## ISO v1.28.0 — the console stops showing the pairing code once the box is connected (2026-09-16, R-535) — PUBLISHED 2026-09-16
|
||||
|
||||
**The defect, measured on a fresh box 2026-09-16:** 25 minutes after a successful bind AND claim, with
|
||||
four apps deploying, the physical console still read „a doboz készen áll, és a párosításra vár" with
|
||||
@@ -16,7 +16,7 @@ waiting will update it.
|
||||
claim-aware console needs a different owner. R-535 is closed for the measured complaint — the code
|
||||
stays on screen after binding — and that residue is recorded rather than implied away.
|
||||
|
||||
## ISO v1.27.1 — the FIRST boot is Felhom's too (2026-09-14, R-496) — NOT PUBLISHED
|
||||
## ISO v1.27.1 — the FIRST boot is Felhom's too (2026-09-14, R-496) — PUBLISHED 2026-09-15 (the marker read NOT PUBLISHED until 2026-09-16; it was published on the big night and the heading was never corrected)
|
||||
|
||||
**Why 1.27.0 was not enough, measured on its proof install (VM 331, screen s20):** `pvebanner.service` ran
|
||||
at the first boot before `felhom-bootstrap` could mask it, so the household's first screen still carried
|
||||
|
||||
Reference in New Issue
Block a user