diff --git a/surfaces/quickshell/patches/README.md b/surfaces/quickshell/patches/README.md
index a447c86..ebe8e8f 100644
--- a/surfaces/quickshell/patches/README.md
+++ b/surfaces/quickshell/patches/README.md
@@ -121,10 +121,14 @@ independent lanes and can go whenever.
   password rather than finger until that check widens — one line, and a
   security decision that is Casey's.
 - **0007 — render context occupancy; stop reading hyprctl errors as cursor.**
-  **Blocked on the server.** Needs `f266136` running, not merely installed.
-  As of 2026-08-12 the box runs `souveraine 0.1.r442.gfb5e9bb80cac-1`, and
-  `fb5e9bb` *predates* `f266136` — edge has not rebuilt. Applied early the pill
-  honestly shows `—`, which looks exactly like the patch failing.
+  **Unblocked 2026-08-12 17:30.** It needed `f266136` *running*, not merely
+  installed. The box now runs `souveraine 0.1.r463.g715080bbfe45-1`, started
+  17:26:45 against a binary installed 17:22, and `git merge-base --is-ancestor
+  f266136 715080b` passes — so the named-field fix is in the live server.
+  Re-verify with that one command before applying; installed is not running.
+  (Earlier state, kept because the *shape* recurs: the box ran r442 = `fb5e9bb`,
+  which predates `f266136`, and applying early makes the pill honestly show `—`
+  — indistinguishable from the patch failing.)
   The bug it fixes: `ContextPressure` crossed a module boundary as a
   **positional tuple**, so every consumer guessed what the second element was.
   The TUI guessed `limit` and was right; the HTTP layer named it `tokens` and
@@ -133,6 +137,15 @@ independent lanes and can go whenever.
   shim), so it runs under viewtop, fails, and its error text is captured **as
   the cursor position** — the probe tested whether the tool was installed, not
   whether it answered.
+  **Before building the click-through breakdown on top of this**, read
+  `tasks/context-accounting-two-counters-2026-08-12.md` in memory. The pill
+  renders the *payload* (what is in the model's window); the
+  `/v1/conversations/:id/tokens` endpoint renders the *archive* (what the
+  transcript weighs). On this conversation they differ by ~3x — 80% against a
+  clamped 100%. Ship them side by side unlabelled and the Panel shows two
+  numbers that contradict each other. Group the breakdown by **block kind**,
+  not by role: 74% of the context is tool traffic, which per-role accounting
+  files under "assistant" and makes it read as talkativeness.
 
 ## Recently closed