1e97d1e637
When slinging work to an agent, updateAgentHookBead() was running bd slot set from townRoot. But agent beads with rig-level prefixes (e.g., go-) live in rig databases, not the town database. This caused "issue not found" errors when trying to update the hook_bead slot. Fix: Use beads.ResolveHookDir() to resolve the correct working directory based on the agent bead's prefix before calling SetHookBead(). Co-authored-by: furiosa <spencer@atmosphere-aviation.com>