felhom.eu/STATUS.md

STATUS — what works, what's broken, what's next

Updated 2026-09-24 (morning session). The fleet is on controller 0.268.0. The undo works after a restore. A stopped app's page tells the truth. A box that is several updates behind now climbs one tested step per press.

Decisions I took on my own: none. Two small changes to your wording, both below.

What I did, and it worked.

• The demo boxes got 0.267.0, as you said yes to. Then, after every live test passed, they got 0.268.0. Both boxes arrived healthy about 15 seconds after each change.
• The undo after a restore. A restore used to rebuild an app's storage without the tag the undo looked for, so the undo copied nothing. Now the undo finds the storage by its name. A restore also puts the tag back. Tested on the scratch machine with an app restored by the OLD version, the way customer boxes are today: the failed update was undone, and data written before and after the restore came back.
• A stopped app's page (your option A). When no copy on the box can bring an app back with its files, the page now says so, says support is informed, and shows no restore button. You get an urgent alarm. Tested by repeating last night's exact case, in Hungarian and English.
• Small fixes. A stopped app no longer raises a second, false alarm. A removed app leaves no old files behind. The test bench now marks a memory test with no real load as "not proven", and it starts every run with an empty drive folder.
• The update ladder. One press now does one tested step, never a jump. Tested with RomM on the scratch machine: first press moved only the app, second press moved only the database engine. The data came back after each press. The page says how many steps remain.

Your wording, changed in two small ways.

• English: I removed the word "please". The house rule for English copy forbids it.
• Hungarian: I kept your text exactly. It uses the formal "Ön" form; the rest of the screens use the informal form. That mismatch is already on the list.

What I found (new, not fixed).

• The second drive cannot bring back an app with files, even though it holds everything. Its restore button refuses such apps, and the file restore brings back only files, not the database. So for Nextcloud, Immich, Paperless and Calibre, only the off-site copy counts. This needs your decision.
• A long crash loop never raises an alarm if the app looks "up" for a moment between crashes. Seen on the scratch machine: 385 restarts, zero alarms.
• The stopped-app sentence says "do not remove the app", but the Remove button is still there. This needs your word.
• Smaller: a ladder step has no health check of its own yet; right after a restore, an update may be judged with the restored health check; one restore option ("database only") is described in the code but offered nowhere.

Rows. Seven closed, six opened. The list went from 336 to 335.

What needs you — two questions.

1. The second drive and apps with files. (a) Build a "files plus database" restore for the second drive (my recommendation — then the second drive is a real way back, as customers would expect). (b) Rule that the second drive is files-only for these apps. If you do nothing, the page keeps naming only the off-site copy for these apps, which is true.
2. The Remove button on a stranded app. (a) Hide it while support is informed (my recommendation — a removal destroys what support needs). (b) Keep it and soften the sentence. If you do nothing, both stay as they are.

Not done. No automatic updates yet (plan part 7). No customer box touched by hand. Nothing on Peti's machine, the off-site box or your own machine was touched, beyond the normal hub update. The scratch machine is back on the real catalog with its standing apps.