# REPORT — controller v0.265.0: R-634's cause fixed, held apps say so, the OOM storm (2026-09-23)

R-634, R-625, R-636, R-647. Commit `0054d4b`. MinAgent 0.131.0 (unchanged). Needs hub v0.121.0 (deployed
first). **Floor raised to 0.265.0.** Full report, the brief's wrong claims, evidence:
`felhom.eu/REPORT.md`, `felhom.eu/documentation/audits/cleanup-2026-09-23/`.

## Not done, or changed
- R-634: the backup race is fixed; the deploy's OWN failure leaving containers is an operator question → R-649.
- R-625: the Update button was already hidden on the list; the fix is the badge (both hold kinds).
- R-636: the flag cannot count (sticky) — the kernel `oom_kill` counter is read instead.
- My first test draft ran real docker on DooPlex (an empty volume) — removed; tests use seams; R-650.

## What shipped
- **R-634:** deploying apps leave `ListDeployedStacks`; the volume leg re-asks (`deployingReporter`) and
  SKIPs; `StopStack`/`StartStack` → `ErrStackDeploying`.
- **R-625:** badge `badge.update.held` „Megállítva — visszaállítás szükséges" / "Stopped — restore needed".
- **R-636:** `ScanOOMKilled` reads `oom_kill`/`memory.max`/`memory.peak`; ≥20 kills in 30 min per container
  run → one `app_oom_storm` (error, operator-only).
- **R-647:** `readerFuncs` (every language) + `UpdateErrorKeyHeld`; `copy_holds` as a key; two log wordings.

## Red-proofs (8 here, each seen failing)
Backup skip; StopStack guard; held badge (v0.264.0 shape); reader funcs; copy_holds phrase; health
severity; storm escalation; counter read. Messages in `felhom.eu/REPORT.md` §3.

## Live (9202)
R-634 race run across a live deploy — the backup stopped three other apps and never the deploying one;
held badge + no button + 409 in all four box/reader language pairs; RomM storm at 21 kills, one line at 49.

`go test ./...` rc=0; `controller_gates.py` rc=0.