dispatch returns 404 for ready EU mirror while regional recap sees checkpoints

Summary

entire dispatch --repos OWNER/REPO returns a service 404 for a ready EU mirror even though the same regional data API reports sessions and checkpoints for that exact mirror.

Environment

• Entire CLI 0.8.42, darwin/arm64
• authenticated account
• source repository mirror: learn-ukrainian/learn-ukrainian.github.io, status ready, aws-eu-central-1
• separate private checkpoint repository mirror: learn-ukrainian/entire-checkpoints-private, status ready, aws-eu-central-1

Evidence

The source mirror's EU recap endpoint is populated:

repoCount=1
team.sessions=4
team.checkpoints=3
team.tokens=116182

The normal cloud dispatch command fails:

$ entire dispatch --repos learn-ukrainian/learn-ukrainian.github.io --since 7d
dispatch service returned status 404: {"error":"Repository not found or not available in its region: learn-ukrainian/learn-ukrainian.github.io"}

The checkpoint repository slug produces the same 404. A direct authenticated POST to /api/v1/dispatches/generate on the EU cell also returns 404 because that endpoint is not exposed there.

The v0.8.42 implementation, and current main, construct cloud dispatch with api.BaseURL() rather than resolving the requested repository's mirror cell. Search and recap already have repository/cell-aware paths elsewhere in the CLI.

Expected behavior

The global dispatch service should resolve a ready mirror in its recorded region, or the CLI should route to a supported repository-aware endpoint. If cross-region dispatch is intentionally unsupported, the CLI should expose a documented region selection or a specific actionable error.

Privacy note

This report contains only repository names and aggregate counts. No checkpoint, prompt, transcript, dispatch, or generated-summary body is included.

Trace the dispatch implementation on main where cloud dispatch uses api.BaseURL(), then compare it with the repository/cell-aware paths used by search and recap. Reproduce the EU mirror request against the documented dispatch endpoint and verify that a ready regional mirror is routed correctly or that the CLI reports a specific actionable limitation.