Generate cloud dispatches on the entire-api cell

[Soph]

https://entire.io/gh/entireio/cli/trails/1535

What

entire dispatch (cloud mode) now generates on an entire-api cell instead of the BFF's POST /api/v1/dispatches/generate.

Why

The BFF route only resolved the repos and read checkpoints from one jurisdiction's cell, picked by ?jurisdiction= or the caller's home. entire-api serves the same generation at POST /me/dispatches, so the CLI can dial that cell itself, the same way activity and recap do.

Changes

• runServer (dispatch/mode_cloud.go) builds one CellClientFactory per run and dials the --jurisdiction cell, or the home cell without the flag. The client is built after the local window and origin checks, since building it already dials.
• The cell route is async: POST /me/dispatches answers 202 with a generating run, and CloudClient (dispatch/cloud.go) polls GET /me/dispatches/{id} every 2s until it is complete or failed. A 3-minute budget outlasts the cell's 2-minute stale threshold. A failed run surfaces its error message.
• Wire types follow the cell's camelCase shape and drop BFF-only fields nothing rendered (branches sentinel, warnings, totals).
• Removed the jurisdiction echo check, since the client picks the cell itself, and the dispatch-local HTTPS guard, since the cell factory already refuses a plain-HTTP data host before sending the login JWT.
• The dispatch wizard reads the home jurisdiction from the same factory through a new CellClientFactory.HomeJurisdiction().
• docs/development/api-routing.md documents cloud dispatch routing. upstream-host-resolution.md no longer lists dispatch as a BFF caller.

Behavior changes

• The cell persists runs, so CLI dispatches now appear in the user's dispatch history on the web.
• A window with no checkpoints fails with the cell's 404 (no checkpoints in window) instead of generating.

Tests

• Cloud client tests cover polling to completion, a failed run, an unknown status, and the poll stopping when the context ends.
• Run tests stub the new newDispatchCellClient seam. TestServerMode_RejectsPlainHTTPBaseURL runs the real cell routing.
• mise run check passes. Not yet exercised against a live cell.

---

Note

Medium Risk
Changes the production dispatch API contract and adds async polling/timeouts; routing and auth now depend on cell catalog resolution rather than the gateway selector.

Overview
Cloud dispatch no longer hits the BFF’s one-shot POST /api/v1/dispatches/generate with a ?jurisdiction= query. It dials the entire-api cell (home or --jurisdiction) via CellClientFactory, posts to /api/v1/me/dispatches, and polls GET /me/dispatches/{id} until the run is complete or failed (202 + generating → terminal status).

CloudClient is rebuilt on shared api.Client instead of a custom HTTP stack; wire JSON is camelCase and the request drops generate / gateway-only fields. Jurisdiction selection is client-side cell routing only—there is no response jurisdiction stamp or checkDispatchJurisdiction guard anymore. Repo-not-found errors still get a home jurisdiction label via new HomeJurisdiction() on the cell factory; the dispatch wizard uses the same factory for defaults.

Docs now describe dispatch under entire-api cell routing and stop listing it on the BFF data-API path.

^{Reviewed by Cursor Bugbot for commit 8ee316e. Configure here.}

[Copilot]

🟡 Changes recommended

The initial POST remains unbounded, allowing a stalled cell response to hang the CLI indefinitely.

1 open finding

• Start dispatch deadline before POST to prevent indefinite request hangs · New

What changed in this PR

Routes cloud dispatch generation directly through the selected entire-api cell and polls asynchronous runs to completion.

Changes:

• Replaces the BFF dispatch endpoint with cell-aware routing and camelCase payloads.
• Adds asynchronous dispatch polling, failure handling, and updated tests.
• Aligns wizard defaults and routing documentation with cell-based dispatches.

File	Description
docs/​development/​api-routing.md	Documents dispatch cell routing.
docs/​architecture/​upstream-host-resolution.md	Removes dispatch from BFF routing.
cmd/​entire/​cli/​auth/​cell_data_api.go	Exposes the factory’s home jurisdiction.
cmd/​entire/​cli/​dispatch/​cloud.go	Implements the new API contract and polling.
cmd/​entire/​cli/​dispatch/​cloud_test.go	Tests asynchronous cloud dispatch behavior.
cmd/​entire/​cli/​dispatch/​mode_cloud.go	Routes dispatches through a cell client.
cmd/​entire/​cli/​dispatch/​mode_cloud_test.go	Updates server-mode routing tests.
cmd/​entire/​cli/​dispatch/​mode_local.go	Removes obsolete data-API seam.
cmd/​entire/​cli/​dispatch/​repo_slug.go	Updates server terminology.
cmd/​entire/​cli/​dispatch/​dispatch.go	Clarifies jurisdiction semantics.
cmd/​entire/​cli/​dispatch/​dispatch_test.go	Updates authentication stubbing.
cmd/​entire/​cli/​dispatch/​consts_test.go	Updates the test endpoint.
cmd/​entire/​cli/​dispatch_wizard.go	Updates home-cell wording.
cmd/​entire/​cli/​dispatch_wizard_scope.go	Resolves wizard defaults through the cell factory.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.