port: my triage under-counted, and three uncited measurements surfaced behind it

Their audit found 9 of 57 HANDOFF sections asserting measured or
undecodable-with-reach citing nothing openable, 84%, including one they had sent
me: '(B) from EXTRAS DOES go black', delivered as an inline frame table while
data/fade-four-transitions.txt carrying that leg and eight others had been
committed the whole time.

It had already landed here uncited. timing.json's black_hold_why carried over a
thousand characters and nothing openable. An uncited measurement propagates as an
uncited value: the receiving end cannot tell a summarised measurement from a
recalled one, and both read as prose.

And my triage had missed it along with seven others. Last iteration I reported 13
provenance claims among the 52 and labelled them; the count was wrong because my
sibling match was literal, so black_hold_why did not match black_hold_units, nor
loop_start_why to loop_start_s, dwell_why to dwell_seconds, loop_leaf_why to
loop_leaf_on_screens. Eight more, all hidden by a suffix. It was 21 and I stated
13 confidently. All eight now labelled from their own text; coverage 16 to 38.

Three uncited MEASURED fields in one file -- loop_why at 1400 chars, loop_start_why
at 1041, voice/presentation_why at 1402 and authored -- and all three were
detailed rather than sloppy. The detail is what made them look sourced: a why that
recounts a measurement carefully reads as well-evidenced because it is careful.
That is the quality-correlated blind spot one level down -- not 'well-evidenced
values never declared themselves' but 'well-argued prose never cited anything'.
The authored one now cites the open question it stands in for.

A false positive in my own extractor surfaced in the same pass: presentation_why
was reported DANGLING on 1118268 and 1171516, byte counts read as commit shas
because they are seven digits of valid hex characters. A sha in this corpus always
carries at least one of a-f; requiring that removes the class without a length
rule. A wrong verdict for a fabricated reason, the fourth of that family and this
time in the auditor.

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

authored/flow.json

@@ -357,6 +357,7 @@
       "SELECT DATA"
      ],
      "skipped_chain_why": "THE PORT SKIPS TWO MEASURED SCREENS HERE, AND IT SAYS SO OUT LOUD RATHER THAN PRETENDING. The real chain is NEW GAME -> DIFFICULTY -> SELECT DATA -> (A) on a save slot -> ~4.5 s -> S00A. DIFFICULTY and SELECT DATA are MEASURED destinations (HANDOFF Q4) but neither is a GP_TITLE build, so there is no screen file to go to. The port jumps from NEW GAME to the one thing in that chain it has, and the runtime prints what it skipped on every run. This is a GAP, not a sequence: nobody may read the port's behaviour here as what the game does.",
+     "skipped_chain_kind": "measured",
      "then_video": "S00A",
      "then_video_why": "P7. HANDOFF Q9, DECODED from the movie manifest: MS00A -> S00A.wmv is the new-game intro, 93.9 s. Its POSITION is measured as well -- the movie starts ~4.5 s after (A) on the save slot, matched off the running game at 0.96-1.000 with a strictly monotone playhead over 25 consecutive 0.5 s samples.",
      "then_video_kind": "decoded",