diff --git a/docs/port/HANDOFF.md b/docs/port/HANDOFF.md
index f3b50a79..e2879ff3 100644
--- a/docs/port/HANDOFF.md
+++ b/docs/port/HANDOFF.md
@@ -78,8 +78,19 @@ authored version can be deleted.
   The elements are `ptlogo_back2.t32`, `ptlogo_back2eff.t32` and
   `ptlogo_back2eff1…5`. 🟡 Those five are also the group with the **known
   unsolved paint-order tie-break** (key `0x8083`) — same screen, same elements —
-  but a blend-order swap explains white-instead-of-pink poorly, so expect a second
-  cause. ❔ Not diagnosed.
+  but a blend-order swap explains white-instead-of-pink poorly.
+  🟡 **A quantified cause for the GEOMETRY**: these elements' declared **pivots do
+  not match their own textures**. `ptlogo_back2`'s pivot `(500,117)` is exactly
+  half the **Japanese** sprite (1000×234), not its own English one
+  (1118×262) — off by **59 px**, the right order to make the swoosh too thick and
+  too far right. 24 of 109 title elements are off by > 8 px, concentrated on
+  `ptlogo*`, and it cuts both ways (the JP build's `ptlogo1` is off by 40).
+  ❔ Whether it *bites* depends on which pivot the compositor uses — **not
+  checked**.
+  🔴 **Ruled out for the COLOUR**: every swoosh keyframe's fade is `0x??ffffff`
+  (white RGB, alpha only), no tint is non-white, and the texture decodes
+  *blue*-leaning (175,174,198). The magenta must come from blending. ❔ Not
+  diagnosed.
   🔴 **Refuted:** it is *not* that our dim covers the whole frame instead of
   sitting beneath the UI — the logo reads +2.36 against a background of −0.74, so
   the paint order is being honoured.
diff --git a/docs/re/METHOD.md b/docs/re/METHOD.md
index b8f2c25f..3186b787 100644
--- a/docs/re/METHOD.md
+++ b/docs/re/METHOD.md
@@ -281,3 +281,9 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
   (odd dimensions rounding), and only **24 off by > 8 px** — and those 24 are the
   real finding, concentrated on one element family. Bucket a mismatch by size
   before reporting a rate.
+* **I have now broken the "read the target text first" rule three times.** Each
+  time a scripted `HANDOFF.md` edit asserted on a paragraph that had been rewrapped
+  by an earlier edit in the same session, and each time the finding landed in
+  `docs/re/` while the port's page kept the stale text. Writing the rule down was
+  not enough; the working fix is mechanical — `grep`/`sed -n` the target paragraph
+  in the same command that patches it, and check the commit's file count.