v0.234.0: a known limitation written on 2026-09-02 was a defect by the next morning
gates / gates (push) Successful in 18s
gates / gates (push) Successful in 18s
The operator looked at demo-felhom and found OpenGist - up 15 hours, running exactly the catalog pin, showing no badge at all. 09-update-architecture.md had recorded that as an accepted limitation the day before: 'the fleet view fills in gradually'. On a quiet box gradually means never, and a feature that fills itself in on an event nobody triggers is, on the quiet installations, not shipped. That limitation row is now struck with the reason kept. The living document gains slice 1b, the two admission rules of the backfill (it never overwrites, and it refuses to seed a partial observation because the badge reads a service-count mismatch as BEHIND), and the note that the same field having two writers with two different admission rules is deliberate. Live evidence added: all nine apps already had records by the time 0.234.0 was ready, so the natural fleet state could no longer exercise the new code - said plainly rather than papered over. The pre-0.233.0 shape was recreated on demo-hp by stripping two records; the backfill re-seeded exactly those two with digests matching independently-read ground truth and left the other seven alone. The refusal half was deliberately NOT staged live: it needs a degraded app, and manufacturing one risks the false-customer-email class that already cost 61 mails (R-330). Unit-tested with a red-proof, and recorded as unproven-live. R-457: a test that hardcodes a date and asserts an age derived from it is green only on the day it is written. Mine was, and it went red overnight. Six other files carry both a date literal and time.Now() - named as candidates, not accused.
This commit is contained in:
@@ -1,9 +1,12 @@
|
||||
# STATUS — what works, what's broken, what's next
|
||||
|
||||
**Updated 2026-09-02 — the box now writes down which version of each app it is running, and shows one
|
||||
**Updated 2026-09-03 — you spotted that OpenGist had no label. You were right, and it was a real gap:
|
||||
the label only appeared on apps something had restarted. Fixed and live (0.234.0). Every app on both
|
||||
machines now carries one. NOTHING IS WAITING ON YOU.**
|
||||
|
||||
**Earlier 2026-09-02 — the box now writes down which version of each app it is running, and shows one
|
||||
small label saying whether it is up to date: „Naprakész" or „Frissítés elérhető — 52 napja". No version
|
||||
numbers, and nothing about updating changed. Both halves are proven on the real machine, labels read off
|
||||
the real pages. NOTHING NEW IS WAITING ON YOU.**
|
||||
numbers, and nothing about updating changed.**
|
||||
|
||||
**Earlier 2026-09-01 (third pass) — the backup work is FINISHED for beta, and I have written down
|
||||
where it stops. One alarm that was telling you something untrue is fixed and live (hub 0.111.1).
|
||||
@@ -116,8 +119,23 @@ nothing.*
|
||||
Full measurement, with the controls and the quoted output:
|
||||
`felhom.eu/documentation/audits/SPIKE-app-update-2026-09-01.md`.
|
||||
|
||||
9. **Nothing here needs you. I got in on my own — after getting it wrong first, which is worth one
|
||||
line.**
|
||||
9. **Nothing here needs you. Two things I got wrong, both now fixed.**
|
||||
|
||||
**You found the first one.** OpenGist showed no label. That was not a misunderstanding — the label
|
||||
only appeared on an app that something had restarted, so an app that simply runs showed **nothing,
|
||||
possibly for months**. On a quiet machine that is every app, which is exactly the machine we most
|
||||
want to be able to look at. **Now the box reads what every app is on when it starts up, and writes
|
||||
it down.** It only looks — it starts nothing and changes no app. Live on both machines: all nine
|
||||
apps on the HP now carry a label, and so does OpenGist.
|
||||
|
||||
**One thing to expect, so it does not look broken:** the label says **„Naprakész"** when an app is
|
||||
on the newest version, with **no number at all**. A number only appears when the app is *behind* —
|
||||
and then it is how long the newer version has been waiting, not how old the running one is. That
|
||||
was your ruling and I think it is still the right one.
|
||||
|
||||
**The second one was mine and smaller:** a test I wrote pinned a date and an age, so it passed the
|
||||
day I wrote it and failed the next morning. Fixed, and I have written down that the same trap may
|
||||
sit in six other test files — named, not accused; someone has to read them.
|
||||
|
||||
The box now writes down which version of each app it is really running, and shows the customer one
|
||||
small label: **„Naprakész"** or **„Frissítés elérhető — 52 napja"**. No version numbers — a
|
||||
|
||||
Reference in New Issue
Block a user