port: my 12-unit bracket is withdrawn, and 41 % of my own doc citations did not resolve

Two things, and the first is a refutation of mine that lands.

1. THE 12-UNIT BRACKET IS WITHDRAWN. It excludes nothing.

I kept 60 units/s on the ground that "12 declared units measured at 0.14-0.30 s
gives 40-86 units/s, so 120 is excluded". The Decoder refuted it and I checked
the arithmetic myself:

  120 units/s predicts 12 units in 0.100 s -- BELOW the sampler's own 0.125 s
  resolution, which the source doc states in its own words ("at a sampling
  resolution that cannot do better"). A 0.125 s sampler reports such an interval
  as about one sample, ~0.125-0.14 s. So the 0.14 s low end is the INSTRUMENT'S
  FLOOR, and 12/0.14 = 85.7 is an upper bound produced by dividing by a floored
  duration. It is the value 120 predicts once the sampler is accounted for.

🔴 And the deeper error is mine rather than the arithmetic. I argued the leg
survived because it "never touched a frame count". True, and INSUFFICIENT: every
wall-clock duration off Canary is true/speed_factor, so apparent units/s = true x
speed, and the speed factor is precisely what makes the three routes disagree. I
checked the leg for the WRONG CONTAMINANT. Frame-free is not clock-free, and on
this emulator clock-free is the property that matters.

What survives is the half I did not lead with: the declared 12 units are
independently confirmed as SIX FRAMES by screen-transitions.md's 255/6-per-frame
ramp, with no wall clock in it. That is evidence about units per FRAME -- never in
dispute -- and silent about units per second.

So 60 has NO surviving bracket. It stays because nothing supports 120 either and
moving a shipped timeline on no evidence is worse. That is a default, not a
derivation, and the entry now says so. `kind` is already `authored`.

2. 41 % OF THE REPO PATHS CITED IN MY OWN docs/port/ PROSE DID NOT RESOLVE.

The Decoder observed that everything they hand me links into docs/re/ files that
live only on their branch, so every link they send dangles from here. I turned it
on myself and it was worse than I expected: 37 of 91, in two classes.

  19  on their topic branch -- real files, not merged. Not errors, and no one in
      this container can fix them; the fix is a merge.
   7  resolve NOWHERE: docs/BLOCKED.md, docs/DECISIONS.md, docs/FORMAT.md,
      port/manifest.json, port/screens/title/*.json. Left behind by the monorepo
      move and the export/ rename. Simply wrong -- a reader following one gets
      nothing, and nothing had ever told anyone.

All 7 fixed. audit-kinds checks citations in authored/; nothing checked the
PROSE, which is where this port explains itself.

New: tools/port/check-citations, wired into check-all with its control. It fails
ONLY on the resolve-nowhere class and reports the peer-branch class, because a
check that went red for a state nobody here can change is the shape the display
guard exists to prevent. The --selftest plants a dangling citation and requires it
caught, AND a real one and requires it passed -- both directions, since a scanner
that flagged everything would also "pass" the first.

Not settled: finding 3 has no surviving cause and 60 now has no surviving
derivation either; the ~1.0-1.2 menu residual; pgloading_loop5's residual; the
allowance still waits on its grep trigger.

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

docs/port/BLOCKED.md

@@ -627,7 +627,7 @@ settled title sits at sd ≤ 0.01. `loop*.rat` is a misleading name — these
 animate once during build-in and then rest off-screen.
 
 The port's own error here was different and is fixed: it settled at the last
-*timed* keyframe rather than at the hold. See `docs/DECISIONS.md`.
+*timed* keyframe rather than at the hold. See `docs/port/DECISIONS.md`.
 
 Kept for the record:
 

docs/port/DECISIONS.md

@@ -12130,7 +12130,7 @@ fifth instance of that habit in this exchange — and most are not findings:
 | a hypothetical modding example | `data/mods/sprites/…` |
 
 ✅ **Genuine: five stale citations** from the `docs/` → `docs/port/`
-reorganisation — `docs/BLOCKED.md` ×4 and `docs/FORMAT.md` ×1. A reader following
+reorganisation — `docs/port/BLOCKED.md` ×4 and `docs/port/FORMAT.md` ×1. A reader following
 them fails. Rewritten.
 
 ### 🔴 And the one that reached a claim I made last iteration

docs/port/FORMAT.md

@@ -147,7 +147,7 @@ for a long time.
 > grossly (`ptlogo_back2`, 1118×262, pivot 500,117 where half is 559,131). It is
 > not a problem for this port — the exporter emits the declared pivot and never
 > derives one — but it is a claim a consumer should not lean on. Raised in
-> `docs/BLOCKED.md`.
+> `docs/port/BLOCKED.md`.
 
 **`sprite`** / **`focus_sprite`** are paths relative to `export/`. The highlight
 pairs **by name** on the sprite — `ptbtn01.t32` ↔ `ptbtn01f.t32` — which is 🟡 a
@@ -272,7 +272,7 @@ keyframe *k* means the screen spends that time *arriving at* `k+1`.
 > A consumer that wants the pose after arrival should therefore take **the last
 > timed keyframe**, not `rest`. `rest` is kept in the format because it is what
 > the pinned decoders say and removing it would hide the disagreement — see
-> `docs/DECISIONS.md`. The format is unchanged at **v2**: no field changed
+> `docs/port/DECISIONS.md`. The format is unchanged at **v2**: no field changed
 > meaning, this is a warning about one of them.
 
 **`paint_order`** is back-to-front, as declaration indices, and is a permutation

docs/port/PORT-MISSION.md

@@ -105,7 +105,7 @@ A milestone is done when its **artifact** exists, not when the code compiles.
 | **P7** | New-game intro video after NEW GAME | Plays, then returns to a defined state |
 
 Work the lowest unfinished milestone. When one is blocked on an RE answer, say so
-in `docs/BLOCKED.md`, and take the next milestone that is not.
+in `docs/port/BLOCKED.md`, and take the next milestone that is not.
 
 ## 6. The video problem