The other agent got a value wrong by resolving a record BY NAME and stopping at
the first hit; their census puts 1467 of 15493 elements (9.5%) behind a second
link, and they asked how exposed this exporter is.
Measured: NOT AT ALL. 135 links resolve -- 116 through a focus block's record, 19
to a top-level element on the same screen -- and 0 reach nothing. Now a standing
check, because this port is adding archives and a link into a record the exporter
does not emit would be invisible: the element still draws, it just silently loses
whatever that record animates.
🔴 THE CHECK'S FIRST VERSION REPORTED 116 FALSE FAILURES, including
ptbtn00 -> ptbtn00f.rat, which I had verified by hand an hour earlier. It compared
the link against the focus ELEMENT's (a .t32) instead of the focus
BLOCK's (a .rat). Caught only because one row was already known to be
right -- a new check producing a confident wrong answer is exactly what its own
subject matter is about.
🔴 And its selftest printed 'passed=False -> ok' in one line: the message
restated the condition as og==1 while the verdict tested og==2. The same stale
restatement bug hit fit-trajectory earlier today, so the message is now DERIVED
from the verdict rather than written twice.
Selftest covers both resolution routes, including the .rat/.t32 mismatch that
broke v1. In check-all.
639bdf1a25