Bryan Helmkamp 649b57c185 feat(api): expose web_url on run responses and run.created event ... So that CLI and other API consumers can surface a clickable link to the run's web UI page instead of guessing route shapes or probing settings. The server populates `web_url` from `server.web.enabled` and `server.web.url`, returns it on `RunStatusResponse` (create plus all lifecycle transitions), and persists it on the `run.created` event so attach replays the same link without re-deriving it. CLI: prints `Web UI: <url>` as a run-header info line, driven off the replayed event so fresh runs and `attach` share one code path. Absent when the UI is disabled. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-03 18:18:19 -04:00
..
brainstorms	docs: capture cargo dev cleanup requirements	2026-04-25 19:14:16 -04:00
ideation	docs	2026-04-09 17:24:30 -04:00
internal	refactor(workflow): split event module by responsibility	2026-05-02 14:52:10 -04:00
plans	chore: plans	2026-05-03 13:10:04 -04:00
public	feat(api): expose web_url on run responses and run.created event	2026-05-03 18:18:19 -04:00
superpowers	chore: plans	2026-05-03 13:10:04 -04:00