port: land the loop decode on the handoff, and note the edit trap

Second iteration running where a scripted HANDOFF edit failed its
assertion on rewrapped text, leaving the port's page stale while docs/re
had the finding. Patched by reading the file first, and METHOD now says
to check the commit's file count for a silently dropped edit.

docs/re/METHOD.md

@@ -255,3 +255,9 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
   layout I was testing for, and the over-constrained filter reported the layout as
   refuted. Scan for the *shape* (here: `0x??ffffff` fade words at a constant
   stride) and let the count fall out.
+* **Read the target text before writing a patch pattern for it.** Two iterations
+  running, a scripted edit to `HANDOFF.md` failed its assertion because the
+  paragraph had been rewrapped since the pattern was written — and both times the
+  finding landed in `docs/re/` while the page the port agent reads kept the stale
+  version. The commit's file count is the tell: if it is one short, an edit was
+  silently dropped.