re(ui): rotation is not nested-only, and the pivot-anchored scale is measured

Two corrections and one new confirmation, all from finishing the sweep I
left running last iteration.

Refuted, by my own sweep, within the hour: "rotation appears to live only
in nested .rat leaf records". That held for GP_TITLE, GP_BUNK and
GP_CHALLENGE -- the three archives the sweep had reached when I wrote it
-- and fails on GP_DIALOG and GP_DEBRIEFING_PILOTLOG, which rotate
top-level elements. Scoping the claim made it cheap to withdraw, but the
sentence should have waited for the sweep.

Those top-level cases are the best evidence on the disc, and they show up
in `screen info --geometry` without a hex dump. GP_DIALOG build 0:
pceff03/pceff04 ramp r = 90 -> 30 -> 10 -> 3 -> 0 while alpha ramps
0 -> 255 and they slide into place -- a swing-in settling upright. Build
6: pzeff02 ramps 43 -> 61 -> 75 -> 90 while scaling 112% -> 200% and
fading to 0 -- a spin-out. Rows committed as reference data.

New: the pivot-anchored scale term in blit, kf.x - pivot*(scale-100)/100,
was implemented and reasoned about but never measured, because every
element previously examined sits at 100% scale where the term is exactly
zero. The ptloop pair scale 600% and 800%, where it is worth 450 and 630
px. Formula predicts centre y = 360.0 for both; capture measures 359.1
and 360.0. Top-left anchoring predicts 810 and 990. Horizontally it makes
t-from-position agree with t-from-alpha to 0.33 / 0.65 units against ~8
without it.

That agreement does NOT prove linear interpolation -- both fields were
inverted through the same linear map, so a shared easing curve cancels.
It shows position and alpha ride one shared parameter. Recorded as such.

The disc-wide sweep is still running; the count is incomplete, the
existence is settled.

docs/re/METHOD.md

@@ -344,3 +344,17 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
   `a=alpha r=rot°` matched the ` r=` pattern. A uniform count across
   heterogeneous inputs is the tell. Make the pattern require the *value*
   (` r=-?[0-9]+`), and sanity-check that a known-negative build reports zero.
+* **A pattern over the archives you happened to check is not a negative.** I
+  wrote "rotation appears to live only in nested leaf records", correctly scoped
+  to the three paks I had swept — and the sweep refuted it on the fourth, within
+  the hour, because the alphabet had not reached `GP_DIALOG` yet. Scoping the
+  claim was what made it cheap to withdraw, but the better move is to let the
+  sweep finish before writing the sentence at all: a negative that is still
+  running is not a finding, it is a prediction.
+* **A field that is implemented is not a field that is measured.** The
+  pivot-anchored scale term had been in `blit` for months and reasoned about in
+  the handoff, and no capture had ever exercised it, because every element anyone
+  had looked at was at 100 % scale where the term is identically zero. Look for
+  the case that makes a term *large* — here 600 % and 800 % scale, worth 450 px —
+  and check it there. A term you cannot distinguish from zero has not been
+  verified by any amount of agreement.