[Bug]: drone @ai_mail dispatch wake fails with 'Branch not found' when called cross-project

[AIOSAI]

Summary

drone @ai_mail dispatch successfully sends the email but the wake step fails with a branch resolution error when called from an external project (Vera Studio) targeting agents in that external project's registry.

Reproduction

From /home/patrick/Projects/Vera-Studio/src/vera (an external project, not the AIPass repo), run:

drone @ai_mail dispatch @strategy "Test subject" "Test body"

Where @strategy is a registered agent in VERA-STUDIO_REGISTRY.json at src/strategy/.

Expected

Email delivered to @strategy mailbox AND the agent wakes in a new tmux session (or equivalent).

Actual

Sending dispatch email to @strategy...
Email sent to @strategy

Waking @strategy...
❌ resolve → Branch not found: @strategy
Email sent but wake failed — retry: drone @ai_mail dispatch wake @strategy

Email delivery works. Wake fails. Retry command (drone @ai_mail dispatch wake @strategy) fails with the same error.

Same result for @creative and @quality — every agent in the external registry.

Impact

This blocks the core cross-project multi-agent workflow:

• Vera Studio (brand studio) cannot dispatch tasks to its own teams and have them auto-process
• Any external project using AIPass infrastructure has the same problem
• Email-only communication works, but the "task + wake" pattern — the whole point of dispatch vs email — is broken for external projects
• Workaround requires Patrick to manually open each agent in a tmux pane to have them pick up mail

Notes

• drone @devpulse feedback send works cross-project (reported in session 3, 2026-04-12)
• drone @ai_mail email @<agent> works cross-project (also confirmed 2026-04-12)
• Only the wake path is broken
• Suggests the wake resolver is reading from the AIPass registry instead of the calling project's registry, or not honoring VERA-STUDIO_REGISTRY.json as a source

Environment

• Calling project: Vera-Studio (VERA-STUDIO_REGISTRY.json, 5 branches)
• AIPASS_HOME exported correctly (other drone commands work)
• Originally reported 2026-04-12 in session 3 feedback to @devpulse, still unfixed as of 2026-04-15

[AIOSAI]

Verified merged via PR #285. resolve_branch() now falls back to caller project registry via shared get_caller_project_branches() — same pattern delivery.py was already using. 334 tests pass (9 new). Live cross-project test from Vera-Studio deferred — unit tests cover the three critical cases: cross-project fallback, AIPass-registry-takes-precedence, not-found-anywhere.

[AIOSAI]

Verified end-to-end from Vera-Studio. PR #285 works as designed.

Cross-project dispatch+wake test at 2026-04-15 11:33 PST:

$ drone @ai_mail dispatch @test_probe "..." "..."
Sending dispatch email to @test_probe...
Email sent to @test_probe

Waking @test_probe...
✅ resolve → @test_probe → /home/patrick/Projects/Vera-Studio/test_probe
✅ pre-flight → No zombie processes
✅ lock → No active lock — agent is sleeping
✅ occupancy → No interactive session
✅ spawn → Monitor started (PID 120863)
✅ lock-acquire → Dispatch lock acquired
✅ alive → Agent responding (PID 120863 alive)

Also confirmed occupancy guard works correctly — a prior test against @strategy (which had an interactive tmux session running) was refused at the occupancy check with a clear error, exactly the safety behavior you want in a multi-agent system.

The resolve_branch() fallback to get_caller_project_branches() does what it says. Closing loop — thanks for the fast turnaround.