R-234 root-caused and CLOSED; R-218's state field corrected

R-234 was filed as "toggling an app on leaves it without a bundle, so the first run
skips it". Measured on demo-hp: that state does not survive a run — the off-site
run's own pre-dump phase calls captureAllRecoveryUnits for every DEPLOYED stack,
through admitApp, before the push, and a unit moved aside was RECREATED.

The actual cause was the single-flight: the manual run was dropped because an
earlier one was still going, runOffboxBackup returned nil, the handler had already
answered "A tavoli mentes elindult", and the card then showed the PREVIOUS run's
green verdict. Fixed in controller v0.205.0 and proven live on demo-hp: a second
request while one is in flight now says "Mar fut egy tavoli mentes — ez a keres nem
inditott ujat. A most lathato eredmeny meg a korabbi futase", as a flash_error.

Independently, and a real gap on its own: a run that skipped an app the customer
selected is now `incomplete`, not `ok`. Selected+deployed with no unit counts;
selected-but-undeployed is named with what to do but does NOT count, because a box
left amber by an app somebody removed is a status nobody reads.

R-218's state field read REOPENED while the same row's body already recorded the
fix shipped in v0.203.0 and proven live. Corrected to CLOSED, keeping the
over-claim history — it is why the row is worded as it is.

Capability map: the off-site capture row's `incomplete` sentence widened to cover a
whole-app skip, and it still does not claim a newly-selected app is protected by
the next run — for a deployed app it is, for an undeployed one the card says so.

Still open, deliberately: R-213, R-202, R-214, R-235.

STATUS.md

@@ -24,6 +24,15 @@ code was wrong. *(CAMPAIGN 11)*
 
 ## What's broken
 
+- **A backup could report „✓ Rendben" while quietly leaving out an app the customer had just
+  chosen — FIXED 6 August.** Two things were wrong and only one had been guessed at. The machine's
+  own rule said *"a warning beside a success is read as a success"*, and it applied it to an app
+  missing a *folder* but not to an app left out *entirely*; that now counts too. And the real cause of
+  the case we saw: pressing „Távoli mentés most" while a backup was already running answered
+  „elindult" and then showed the **previous** run's green tick — so the customer read it as covering
+  their new app. It did not, and the restore refused minutes later. The button now says plainly that
+  it did not start anything.
+
 - **A machine installed today still gets the older in-house service, so it cannot open a recovery
   package until you approve the newer one.** It is no longer *lied to* — it says plainly that the
   machine cannot do this yet — but **approving the new service is one click from you**, and until then