Web runs go through the browser extension only: claude --cloud is gone

[suleimansh]

🤖 automated — the follow-up Rom asked for on Discord ("remove it once the extension has proven itself"; #1693 proved it, and he 👍'd "land #1328 first, then drop --cloud").

What

• driver/cloud.ts: the extension path is the only path. Gone: the script pty runner, CLOUD_COMMAND / CLOUD_ENV, the ANSI + session-URL scraping, RunPty / AgentPtyOptions, the bin option.
• The trust write is gone too — claude-trust.ts + tests + specs deleted, FEATURES-SPEC line dropped. It existed (Paper cut: "Claude Code has not been trusted in this project" #1493) only because the CLI asked its folder-trust question under the daemon's pty (claude-web: every run fails with 'no cloud session was created' when the project root is not trusted by Claude Code #1314); no CLI runs for a web hand-off any more.
• The former fallbacks are named errors, each its own cure: a run no daemon started → start web runs from the dashboard; no GitHub remote → the project needs an origin on GitHub; 409 → install or reload the extension, keep the browser bridge on; 404 → turn the browser bridge on in Settings. A failed anchor push fails the run — the session must open on that ref. Waiting past the timeout names the extension.
• cli.ts: the "no GitHub remote → bundle upload" line is gone; the hand-off notice says the extension creates the session.
• Specs: cloud.SPEC.md + test spec rewritten; cli, daemon-runtime, bridge-starts, web-start-endpoints, cloud-session-link specs adjusted; FEATURES-SPEC's web-run line now says what a run without the extension does.

Verified

• typecheck clean; framework 1583/1583; dashboard 834/834 (one flake on the first run, green on rerun — no dashboard code in this PR); extension harness green.
• Break-check: dropping the 409 error fails the named-cure test; restored, 19/19 cloud tests.
• Dogfood: see the comment below (a real web run on gemstack through this build).

Not in this PR

• claude --teleport stays in the hand-off summary and the cloud notice: it is how a person continues a session locally, unrelated to how it was created.
• Model selection on the extension path (the page's default; follow-up).

[suleimansh]

Dogfood on this build (daemon restarted on drop-claude-cloud, extension 0.11.0): run 2026-08-24T16-45-22-929Z on gemstack → asked the browser extension to create the cloud session on framework/the-framework at cloud-1-e7b54b00 → session_01Y4wHy5w7CzDQc61jibjqsU → run ended ok, hand-off pushed. No CLI involved.

🤖 automated