port: the clock freezes at settle -- my window is the game's, and the boot is known too fast

The Decoder measured build 4's top-level clock stopping inside [160,236]. The
exporter computes title's settle window as [160,236,198] from the file alone.
Same interval, two independent methods -- the first evidence for the settle
instant that does not come from our own renderer. ptcopyright reaching alpha
255 exactly at t=160 agrees from a third direction.

Corrects a claim in three places: timing.json, flow.json and boot.gd all said a
screen's dwell IS its keyframe group and the port reproduced 'the disc's own
pacing'. Build 4 declares ~120 presented frames and dwelled ~1100. The decision
to hold zero extra stands; the claim that it was faithful does not.

Checks their two declared spans against the file: both exact, with a 106-vs-105
interval-convention quibble that changes nothing.

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

authored/flow.json

@@ -44,13 +44,32 @@
  ],
  "dwell": {
   "_": [
-   "DELIBERATELY EMPTY. Each screen's dwell is its own keyframe group -- the",
-   "publisher wordmark reaches its hold at t=235 (3.92 s) and the developer",
-   "logos at t=190 (3.17 s), both read from the disc. Holding beyond that would",
-   "be a number nobody has measured, so the sequencer holds for zero extra time",
-   "and the pacing is the disc's own.",
+   "NOT SET -- and the reason is no longer the one this key used to give.",
    "",
-   "When a capture times the real boot, the extra hold per screen goes here."
+   "🔴 It used to say \"a screen's dwell is its OWN keyframe group\". That is",
+   "REFUTED, measured in the draw stream by the Decoder on 2026-08-29",
+   "(docs/re/structures/ui-clock-freezes-at-settle.md): GP_TITLE build 4 declares",
+   "t = 0..269, about 120 presented frames at that capture's pacing, and the real",
+   "dwell lasted ~1100 -- roughly NINE TIMES its own timeline. The top-level clock",
+   "advances through the build-in, STOPS inside the settle window, and holds. The",
+   "exit ramp is not on a timer; it plays when something makes the screen leave.",
+   "",
+   "So the group is not the dwell, and a port that leaves when the group ends is",
+   "not reproducing the disc's pacing -- it is leaving at the moment the game",
+   "starts waiting.",
+   "",
+   "The DECISION is unchanged and still right: hold zero extra rather than invent",
+   "a number. What changes is what may be claimed for it. The boot is KNOWN TOO",
+   "FAST on every screen it plays out, by an amount nobody has measured. It is not",
+   "'the disc's own pacing'; that phrasing said the port was faithful here, and it",
+   "is not.",
+   "",
+   "⚠️ Only build 4 has been measured, and build 4 is the one screen where the port",
+   "is unaffected -- it is the boot's end state and holds indefinitely anyway. The",
+   "two screens this actually governs, publisher_logo and developer_logos, are",
+   "UNMEASURED. Nothing here may be read as a number for them.",
+   "",
+   "If a capture ever times the real boot, this is where that number goes."
   ]
  },
  "navigation": {

authored/timing.json

@@ -26,11 +26,30 @@
  ],
  "dwell_seconds": null,
  "dwell_why": [
-  "NOT SET, and not needed. A screen's dwell is its OWN keyframe group: the",
-  "publisher wordmark reaches its hold at t=235 (3.92 s) and the developer logos",
-  "at t=190 (3.17 s), both read from the disc. Adding a hold on top of that would",
-  "be inventing a number nobody measured, so the sequencer holds for zero extra",
-  "time and the pacing you see is the disc's own.",
+  "NOT SET -- and the reason is no longer the one this key used to give.",
+  "",
+  "🔴 It used to say \"a screen's dwell is its OWN keyframe group\". That is",
+  "REFUTED, measured in the draw stream by the Decoder on 2026-08-29",
+  "(docs/re/structures/ui-clock-freezes-at-settle.md): GP_TITLE build 4 declares",
+  "t = 0..269, about 120 presented frames at that capture's pacing, and the real",
+  "dwell lasted ~1100 -- roughly NINE TIMES its own timeline. The top-level clock",
+  "advances through the build-in, STOPS inside the settle window, and holds. The",
+  "exit ramp is not on a timer; it plays when something makes the screen leave.",
+  "",
+  "So the group is not the dwell, and a port that leaves when the group ends is",
+  "not reproducing the disc's pacing -- it is leaving at the moment the game",
+  "starts waiting.",
+  "",
+  "The DECISION is unchanged and still right: hold zero extra rather than invent",
+  "a number. What changes is what may be claimed for it. The boot is KNOWN TOO",
+  "FAST on every screen it plays out, by an amount nobody has measured. It is not",
+  "'the disc's own pacing'; that phrasing said the port was faithful here, and it",
+  "is not.",
+  "",
+  "⚠️ Only build 4 has been measured, and build 4 is the one screen where the port",
+  "is unaffected -- it is the boot's end state and holds indefinitely anyway. The",
+  "two screens this actually governs, publisher_logo and developer_logos, are",
+  "UNMEASURED. Nothing here may be read as a number for them.",
   "",
   "If a capture ever times the real boot, this is where that number goes."
  ],