diff --git a/docs/re/METHOD.md b/docs/re/METHOD.md
index e790114e..f34dd67f 100644
--- a/docs/re/METHOD.md
+++ b/docs/re/METHOD.md
@@ -562,6 +562,25 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
   nothing later re-opens them. The check here cost one `screen info` invocation
   against a claim I had already written into `HANDOFF.md` twice.
 
+  📌 **And `sylpheed-port`'s corollary, which is the sharper half: distrust them
+  hardest when SOMEONE ELSE writes them**, because they arrive without the doubt
+  the author would have had. They copied my "EXTRAS is stuck at n=1 — a structural
+  limit" out of a message into `DECISIONS.md` as an established fact **while
+  holding the file that refuted it** — their own `authored/flow.json`, recording
+  `ptbtn11` → `GP_MISSION_SELECT`. The protocol says a message carries no evidence;
+  a sentence copied out of one is still a sentence from a message.
+
+  ✅ **Swept this side for the same shape and it is clean** — port-supplied figures
+  are attributed in the text (`"port reports 866 keyframes … 0 untimed"`), the
+  `ui_layout.rs` comment cites **my own** 0-of-24 811 rather than their 866, and
+  their quantisation floor of 0.41 appears in no document of mine at all.
+  ⚠️ Reach: this tests *attribution wording* and the port-supplied figures I could
+  enumerate, not every reliance. 📌 **What protected it was a habit, not vigilance:
+  writing the source into the sentence.** That is the third instance of one
+  remedy — *state what the number is a number of*, *write the index space into the
+  token* (`e10`), *write the source into the claim*. Put the qualifier in the text,
+  never in the reader's memory.
+
 ## Runtime / emulator
 
 * **Look at the PNG** — and check its dimensions.
diff --git a/tools/re-capture/fade_decompose.sh b/tools/re-capture/fade_decompose.sh
index 4d28f432..9347c633 100755
--- a/tools/re-capture/fade_decompose.sh
+++ b/tools/re-capture/fade_decompose.sh
@@ -177,7 +177,15 @@ echo "── EFFECTIVE CONFIG ────────────────
 echo "   requested WHERE = ${WHERE}"
 echo "   branch taken    = ${BRANCH:-<none — no branch set itself, this is a BUG>}"
 echo "   button to press = ${BTN}"
-echo "   arming on       = $(screen)"
+# ⚠️ `screen` is screen_id.py, which CANNOT tell the main menu from EXTRAS --
+# both are dark blue GP_TITLE screens. Reporting it alone announced "menu" while
+# the run was armed on EXTRAS, i.e. a field the guard could not resolve for
+# exactly the two screens in question. An announcement that cannot distinguish
+# the cases it announces is only half a guard. Print both, and the discriminator
+# with its margin, so the ambiguity is visible rather than hidden.
+shot "$OUT/arming.png"
+echo "   arming on       = $(screen)  [screen_id: cannot separate menu/EXTRAS]"
+echo "   discriminator   = $(python3 "$SD/which_title_screen.py" "$OUT/arming.png" 2>/dev/null || echo 'n/a — not a GP_TITLE screen')"
 echo "──────────────────────────────────────────────────"
 [ -n "${BRANCH:-}" ] || { echo "REFUSING: no branch announced itself"; exit 5; }
 xdotool windowactivate --sync "$win"; sleep 1