agent:find returns ricon-family/den for every agent, breaking dispatch for fold-resident agents

[zeke-ricon]

What

shimmer agent:find <agent> returns ricon-family/den for every agent regardless of where their dispatch workflow actually lives. For agents whose workflows live in ricon-family/fold (Quick, Junior, C0DA, Brownie, Johnson, Rho, K7R2), this causes shimmer agent:dispatch <agent> ... to fail with HTTP 404 on the workflow lookup:

HTTP 404: workflow quick.yml not found on the default branch
(https://api.github.com/repos/ricon-family/den/actions/workflows/quick.yml)

The caller has to know the gotcha and pass --repo ricon-family/fold explicitly. That's surfaced friction with no upside; the tool should figure it out.

Affected agents (as of 2026-05-14)

Workflow repo	Agents
ricon-family/den	baby-joel, ikma, zeke
ricon-family/fold	brownie, c0da, johnson, junior, k7r2, quick, rho

Proposed fix

Two clean options:

1. agent:find returns the actual workflow repo per agent. Probably the cleanest — agent:find is supposed to answer "where is this agent's home?" and right now it answers wrong for fold agents.

2. agent:dispatch falls back automatically — try the agent:find result first, on 404 retry against the other collective. Loosens the contract but works without agent:find changing.

Either fix lets a caller use the natural shimmer agent:dispatch <agent> ... form without knowing the workflow-repo split.

Workaround until fixed

Pass --repo explicitly. Documented in fold notes/agent-dispatching.md.

Origin

Hit while dispatching reviews on KnickKnackLabs/notes#82. Captured in fold notes/agent-dispatching.md as a Known Gotcha. Filing here so the workaround can eventually disappear.