port: withdraw 'the boot is known too fast' -- the splash dwells are declared and the port already played them

The Decoder measured both splashes over 3 cold boots: publisher t=0..255,
developer t=0..210, the developer agreeing with wall clock to 1.1%. The port
emits each declared value plus the 9-unit black hold, exactly. No code change.

My error was the generalisation, not the arithmetic: build 4 is the title, whose
exit is caused from outside its timeline, so it holds; a splash's exit is caused
by nothing, so it plays out. I used the one boot screen the port is unaffected
by to overturn the two it governs. Declining to scale by 9x while adopting the
conclusion that implied was half a caution.

Also refutes their two splash boundaries as not comparably anchored: 2.237 vs
2.414 units/frame in one boot, and the publisher has a glow symmetric with the
developer's three.

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

authored/flow.json

@@ -44,32 +44,37 @@
  ],
  "dwell": {
   "_": [
-   "NOT SET -- and the reason is no longer the one this key used to give.",
+   "NOT SET -- because the dwell is DECLARED, and the port already plays it.",
    "",
-   "🔴 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.",
+   "This key has now been wrong in two opposite directions, and the second was",
+   "mine, so both are recorded.",
    "",
-   "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.",
+   "It first said 'a screen's dwell is its OWN keyframe group'. Then GP_TITLE",
+   "build 4 was measured dwelling ~1100 presented frames against a declared ~120,",
+   "and I generalised that into 'the boot is KNOWN TOO FAST on both splashes'.",
+   "🔴 THAT WAS AN OVER-CORRECTION and it is withdrawn. Build 4 is the title: its",
+   "exit is caused by something outside its timeline, so it holds. A splash's exit",
+   "is caused by nothing, so it plays its declared timeline and leaves. The title",
+   "is the exception, not the rule, and one screen was never enough to overturn",
+   "the other two.",
    "",
-   "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.",
+   "MEASURED 2026-08-29 by the Decoder over 3 cold boots",
+   "(docs/re/structures/boot-splash-dwells-are-declared.md):",
    "",
-   "⚠️ 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.",
+   "  publisher  declared t=0..255 = 4.250 s   corpus 4.30 / 4.60 / 4.37",
+   "  developer  declared t=0..210 = 3.500 s   corpus 3.51 / 3.50 / 3.37",
    "",
-   "If a capture ever times the real boot, this is where that number goes."
+   "The developer agrees to 1.1 %, two of its three runs to 0.3 %. The port emits",
+   "4.400 s and 3.650 s -- each declared value plus the 9-unit black hold, exactly.",
+   "So the pacing was right all along and nothing changes in the code.",
+   "",
+   "🔴 AND THE UNIT STAYS UNITS, NOT SECONDS. The same two dwells timed in the",
+   "Decoder's own container came out 15-20 % LONGER than both the declared values",
+   "and the corpus -- same disc, same timeline -- and three independent readings",
+   "of that container's rate disagree with each other. A seconds figure records",
+   "one emulator's pacing on one run. The units are on the disc. If anything ever",
+   "goes in `dwell` it is an extra hold in UNITS, and only for a screen that is",
+   "measured to wait beyond its group."
   ]
  },
  "navigation": {