docs(hub v0.108.0): the delivery grain, the cooldown ruling, and gate 11's first subject

The alarm ladder gains §6.2 - which events are per-app, per-run, per-tier or
coarse, and why the default is coarse. CONTEXT records two rulings: the grain is
allow-listed rather than inferred from the payload, with crossdrive_failed as
the proof that a payload rule would have been wrong; and a finding recorded only
in REPORT.md has a lifetime of one session.

R-389 closed and compressed, keeping its rules and naming the commit whose
git show returns the full text. R-390 and R-391 left open.

REPORT.md is gate 11's first real subject and passes: six observations, two
FILED, four NOT-A-FINDING with their reasons. Three of those declarations are
things a tidier report would have omitted - the gate's own spec would have
passed the item it was built to catch, the burst has no ceiling, and ArgoCD
said "successfully rolled out" while still running the old image.

STATUS carries forward the one thing outstanding: the controller floor still
reads 0.222.0 while the golden reads 0.223.0.

STATUS.md

@@ -1,7 +1,7 @@
 # STATUS — what works, what's broken, what's next
 
-**Updated 2026-08-23 — the app-down alarm now actually reaches you by e-mail. It never has: 91 of
-them were filed and not one was ever sent. Released and NOT yet delivered: step 1 is yours.**
+**Updated 2026-08-23 — you now hear about EVERY broken app, not just the first one each hour. The
+hub deployed itself; nothing is waiting on you except the floor from the last release.**
 
 > **A view, not a source.** `documentation/backlog/OPEN-ITEMS.md` is the authority; this page restates
 > part of it in plain words, and **nothing may exist only here**. **Items, not paragraphs. One screen.**
@@ -12,20 +12,14 @@ them were filed and not one was ever sent. Released and NOT yet delivered: step
 *This section is allowed to be longer than one screen, and each item says what happens if you do
 nothing.*
 
-1. **Vouch the golden carrying controller 0.223.0** — Hub → Configuration → Day-0 artifacts.
-   **It is already baked, published and round-trip verified**
-   (`documentation/tests/golden-0.223.0-2026-08-23/`); only the vouch is left, and only you can do it.
-   **It is a THREE-field save:** `golden_version` → **0.223.0**, `agent_version` → **0.130.0**,
-   `min_agent` → **0.129.0**. **Then** raise the floor to **0.223.0**, last, in its own save.
-   **If you do nothing:** the fleet stays on 0.222.0, where the app-down alarm shows on the dashboard
-   and e-mails nobody, and where an app stopped from outside is still reported as if you had stopped
-   it yourself. New machines still receive 0.222.0.
-   *(The hub half is already live — v0.107.0 deployed itself through the manifest. Nothing owed there.)*
+1. **Raise the controller floor to 0.223.0** — Hub → Configuration, the global floor box, on its own.
+   You already vouched the golden (the hub reads `golden_version` 0.223.0), but the floor still reads
+   **0.222.0**, so the last step of that release is outstanding.
+   **If you do nothing:** boxes are offered 0.223.0 but nothing requires it, so a machine that misses
+   the offer stays on 0.222.0 — where an app stopped from outside is reported as if you stopped it.
 
-2. **A new switch has appeared for your customers, and it is OFF** — „Alkalmazás nem fut". **You get
-   the e-mail either way**; the switch only decides whether the customer also does. This is what you
-   asked for and it needs nothing from you. Mentioned so it is not a surprise the first time you see
-   the settings page.
+2. **Nothing else.** This release changed only the hub, and the hub deploys itself through its
+   manifest. No golden, no vouch, no controller.
 
 3. **Whether to change the hub password** (R-350). I printed it into my own session log on 20 August.
    Not in git, not in any saved file — in the log on this machine. **If you do nothing:** it stays as