re: close the sweep-leaf thread -- deliver it to HANDOFF, and record why one

check counted more than the others

An answer not reachable from HANDOFF is not delivered, and this thread lived in
messages and docs/re/. Delivering it: the leaves ARE drawn and free-run on a
settled title, so a settled screen is not a static screen; the leaves are
identical on entries 4, 5 and 7; how the game advances them is undecodable with
reach, four models each refuted by a measurement; and keyframe_units_per_second
should stay put because the port's 1.87x table has an input now known to be wrong
rather than merely unpinned.

METHOD gains the lesson sylpheed-port named, which outlives the thread. Almost
every cross-check here runs disc -> exporter -> export against disc -> our reader:
two paths that agree because they read the same bytes with the same
understanding, and that agree anyway when the understanding is wrong. That is how
this corpus produced a build-ordinal error where everything still validated, a
two-era comparison with the same binary on both sides, and a rate confirmation
that was a prediction 20 % low meeting a measurement 50 % high. The chain that
counts ends at the ORACLE, and the single instance this week was the leaves'
rotation: +30 / -45 from the file predicting AABB heights of 1135.3 and 1301.1
against 1134 and 1303 in the draw stream. Before quoting an agreement, ask where
the two paths diverge -- if it is after the fact in question they are one witness
wearing two coats.

Also records that a refuted model is a result: four refutations, each with the
measurement that closed it, is firmer than any one of them fitting would have
been, because the failure this corpus keeps hitting is a model that fits for the
wrong reason and nobody checks.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v

docs/re/METHOD.md

@@ -376,6 +376,30 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
   or exclude `$$`. Three instances in one session is not a footnote — reach for
   `-C` first and use `-f` only when the name genuinely is not enough.
 
+* **Two paths that share a source are one witness.** Almost every cross-check in
+  this project runs *disc → exporter → export*, verified against *disc → our
+  reader* — two routes that agree because they read the same bytes with the same
+  understanding. When that understanding is wrong they agree anyway, which is how
+  this corpus produced a build-ordinal error where "everything still validates", a
+  two-era render comparison with the same binary on both sides, and a rate
+  "confirmation" that was a prediction 20 % low meeting a measurement 50 % high.
+  ⚠️ **The chain that counts ends at the oracle**: *disc → exporter → export →
+  **the running game***. The one instance this week was the sweep leaves' rotation
+  — `rotation_deg` +30 / −45, read from the file, predicting a rotated quad's AABB
+  height at 1135.3 and 1301.1 against **1134** and **1303** measured in the draw
+  stream, both under 0.2 %. Two angles, two scales, one independent endpoint.
+  Before quoting an agreement, ask **where the two paths diverge** — if it is after
+  the fact in question, they are one witness wearing two coats.
+
+* 📌 **A refuted model is a result, and four of them are a strong one.** The
+  leaf's clock ended *undecodable with reach* after frame-locked, wall-clock,
+  fixed-wall-clock-sampling and per-UI-drawing-frame were each refuted **by a
+  measurement**. That is a firmer statement than any of the four would have been if
+  one had happened to fit — because the failure this corpus keeps hitting is a
+  model that fits for the wrong reason and nobody checks. Record the closed routes
+  with the number that closed each one; a negative with reach is deliverable, and a
+  fit without a residual is not.
+
 ## Runtime / emulator
 
 * **Look at the PNG** — and check its dimensions.