diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md
index e25c36b..3bc704e 100644
--- a/WORK-QUEUE.md
+++ b/WORK-QUEUE.md
@@ -3989,6 +3989,37 @@ Not acceptable substitutes: re-verifying the served Helm page's FRESH/STALE stat
 unit), and any further digest of `recoveries/summary-fidelity-pilot.md` — that file is only what the
 alphabetically-last selection returns, and `MERCURY_CHECK_ARTIFACT` now sets the target deliberately.
 
+**Landing note — PR #72 merged into `timmy-talking-turd`, 2026-10-11 12:02:42Z (control plane 12:28Z).** `main`
+is now **`a1777a72e`**, a **two-parent** merge of `58b7feddc` and `d9f82299d` — git-level merged, while the Forge
+API reports `merged=false`, `merged_at=null`, `merge_commit_sha=''`. That is the fifth instance of the flag and
+the first with an explanation: the message reads "Merge pull request #72: …" rather than Gitea's button form
+("… (#71) from timmy/… into main"), so this landing never went through the Forge's merge path. Reconcile with
+the git parent count, not the flag. **Issue #18 closed 12:02:43Z**; open issues 37→36, open pulls 7→6.
+
+- The landing is safety-positive and the monitor's re-run holds: corpus `--verify` 7/7 on sha256 **and** byte
+  length; unit suite 122/122 (7 new); the four regenerated screenshots byte-identical to the committed
+  artifacts; `quality.yml` installs chromium before the browser gates; `build_release.py` gains a
+  `vision_corpus_refusal` gate.
+- **The contract question from the 08:17Z tick is now shipped, not hypothetical.** `src/analysis.js` at the
+  merge head is 125 lines and its own comment at `:38` reads "an out-of-range value still fails closed" — but
+  the blank check at `:39-46` returns the `unusable_visual_fields` abstention *before* the range check at
+  `:49-50`, so a reply that is both out-of-range and blank (`{"bristolType": 9, "color": null}`) abstains
+  instead. The corpus labels that class `out_of_range_or_missing_fields → fail_closed` and carries no fixture
+  for the combination (its only out-of-range case has a non-null `"purple"`). Filed as **#73** (area/model,
+  priority/P1) with the repro and two one-line options. Not a safety breach — no prefill, no provider text, no
+  image bytes — and the choice is a build-owner call, not the control plane's.
+- Process, stated plainly: the exact-head hostile review requested at 08:17Z never ran — Praetorian's provider
+  auth was failing at 08:14:35Z ("No Codex credentials stored") — and the head merged at 12:02:42Z. The
+  discrepancy is therefore live in the shipped contract rather than caught before it.
+- Bookkeeping left to the repo owner: `ROADMAP.md:50` still lists #18 unchecked (as do #13 and #20; the map
+  isn't ticked per issue), and epic #2's remaining head item is **#19**.
+- For Alexander: PRs **#60–#65** have been open since **2026-08-22** (~7 weeks) while a 4-hour PR merged inside
+  one window — land them or supersede them?
+
+*(Reading order, for anyone arriving at the end of this file: the 12:04Z Mercury day-3 pin two blocks above is
+superseded by the 12:08Z amendment immediately below this note — the Q25 negative control it pinned was already
+delivered inside Q25's own deliverable §2, so Mercury's day-3 unit is the first slice of Q31.)*
+
 **Amendment, 2026-10-11 12:08Z (control plane, written from the tick that landed
 `replies/2026-10-11-to-mercury-02.md` at `d5a1798`) — the day-3 pin above is corrected: the Q25 negative
 control it pins has already been executed and recorded, so Mercury's day-3 unit is the first slice of Q31, and