Dispatched brief #117 cited a design-doc scratchpad (decision-records-design-doc.md) that wasn't findable via recall/scratchpad_list

Brief #117 (and parent #95) repeatedly reference the full craft doc as `scratchpad decision-records-design-doc.md` for §0/§5/§5.5/§8 — the load-bearing design reference for the PR. As the dispatched worker I could not locate it: scratchpad_list(project 49, query 'decision-records-design-doc' / 'annunciator decision records design') returned 0 hits, and recall_search surfaced session segments about the doc but not the doc itself. It may be archived or living under a different Solo project. The brief spec was thorough enough to implement from (§5/§5.5/§8 were inlined into the #95 spec), so this wasn't blocking — but a dispatched worker following the spec's own pointer hits a dead end. Idea: when a brief spec cites a scratchpad by name, either auto-link it (brief_links) so recall_brief surfaces it, or have recall resolve scratchpad-by-name across Solo projects. Minor, non-urgent.

created

1d ago

triaged

—

resolved

—

resolved by

—