From the Decoder's audit of their own /canary checkout, not from anything visible
on this side. They applied their own lesson rather than stating it, and the
exposure was four logger commits deep, not one.
The sharpest bears directly on what this port shipped. `0f920e645` adds `blend=`
per draw, and without it a draw log records NO BLEND STATE AT ALL -- so
ui-blend-mode-decoded.md's 35-element oracle, the evidence on which this port
DELETED its authored additive map, could not be re-derived by anyone who cloned
this repository. Not approximately. Not at all.
It is reproducible now: four container-only commits exported as patches on their
branch with a rebuild recipe. Named in prose without a resolvable path, since
that directory is not in this checkout and citing it as one would be the exact
defect check-citations exists to catch.
What it changes: nothing is retracted. The measurement was real when made and is
now portable, and the trade was still right -- a screen-name map cannot answer for
a screen nobody drove to, so the decoded field is better regardless. What it
changes is what "decoded" was resting on: for the window between adoption and
export, this port had deleted an authored entry in favour of a field whose
supporting oracle nobody else could regenerate.
📌 Theirs, and the durable line: a finding is only as portable as the tool that
produced it, and a reproduce recipe that READS as complete is the dangerous kind.
Theirs named shas, which is why four commits sat unexported while one was noticed.
⚠️ And this port cannot check the class from here. check-citations scans repo
paths; an instrument living in another container is not a path at all. The only
defence available on this side is asking what produced a number before adopting
it -- which is a habit, not a check, and does not run.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AHUQvXGyNcKonSEWsgWcX
b88e2e38b1