From the Decoder's catch at shutdown, not my own. They found their Canary logger
change -- the texture content hash -- living UNCOMMITTED in /canary, a checkout
pushed nowhere. Two committed findings could not be reproduced without it: it is
the field separating "the buffer rotated" from "a frame was decoded", and its
absence is what cost two withdrawn positions on units/second in one day. They
committed it and exported it into the repo as a patch.
Their generalisation applies here too, so I audited this side at the same moment.
One real instance: DECISIONS.md cited
`/reborn/docs/re/captures/main-menu-oracle.png` as the evidence for a decision.
The capture IS in the repository, at docs/re/captures/main-menu-oracle.png --
only the path was stale, left by the monorepo move. Fixed. The other /reborn
mentions are deliberate: one warns the mount is empty, one is a table row listing
the pattern as an example of what not to do.
⚠️ tools/port/check-citations does NOT catch this class, and the gap is named
rather than quietly left: it scans for REPO paths that fail to resolve, and an
absolute path is not a repo path, so it slips through. Extending it to flag
off-repo absolutes -- especially ones whose basename does resolve in-repo, the
recoverable case -- is the obvious next increment and is deliberately NOT done
here. It was found minutes before a shutdown, and a hasty checker is worse than a
named gap.
Index regenerated.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AHUQvXGyNcKonSEWsgWcX
7a0318c2c0