The RenderingServer rewrite leaked 5 CanvasItem RIDs per run -- exactly the number
of paint-order runs on the main menu. Items created through the server are not
owned by the node; a child Node2D would have been collected for me, and the reason
for not using one is the reason this had to be paid for. Freed in _exit_tree.
Nothing failed. verify-capture was green on every screen and the pictures were
right; the leak line sat next to "N ObjectDB instances were leaked at exit", which
BLOCKED.md records as engine-side and not ours after releasing every reference the
port owns moved the count not at all. A new leak line beside a known-benign one is
close to perfect camouflage. What distinguished it was the number: 5 is a count of
my bands.
Refutation, and it lands. ui-blend-mode-measured.md closes "every element on the
two screens the port ships is in the table except the two above and pteff10".
Checked against my export, counting the summary table's prose rows as coverage:
exactly right for main_menu, and on EXTRAS it misses four -- ptframe4, pteff21,
pteff22, pteff23. Five, not one.
They are not an arbitrary four. They are precisely the elements the port now
measures as the worst on that screen, ptframe4 at 16.19x the frame mean. Every
measured row still stands and the port has transcribed all of them; what is wrong
is the reach, and it is the difference between "one loose end" and the open ask in
BLOCKED.md, which now says so.
Secondary, offered as such: "every button" in the summary row is a class
generalisation in a document that warns its reader to take the table as per-element
facts. No button appears in the EXTRAS draw log at all. Very likely right, nothing
of mine depends on it.
3a3f5bae85