x shot / x pr / x ci: the primary developer is an agent, and an agent cannot look at anything

[sebyx07]

Two gaps that are really one. The framework's stated primary developer is an AI agent. An agent cannot open a browser, cannot look at a running dev server, and cannot read the GitHub web UI. It can read a file, and it can run a command that prints.

x shot <route> — a rendered route, on disk

There is no supported way to get a rendered page into a file. Every app that needs one will grow its own Playwright harness, and each will get the same details wrong. What a first-class one needs:

• boot x dev on a scratch port — not 3000, which another project usually holds — and drive that,
  not the static build (x build --target static prerenders site/ only, so an app/ route
  photographs the landing page and reports its island as missing, which reads as a bug in the app);
• write shot.png and verdict.json: console errors, page errors, mounted island count, canvas
  size. A picture cannot tell you the island threw or logged, and that is the half that gates;
• never in x verify. A gate that needs a browser goes red for reasons unrelated to the change,
  and CI does not install one.

x pr review / x pr resolve / x ci

Addressing a review means reading inline review threads. gh pr view --comments does not show them — it shows issue comments, while the actionable findings are anchored to lines and reachable only through GraphQL. The thread id needed to resolve one exists nowhere else. Every team on Ultimate will rediscover that query.

Same for CI: gh run view prints a tree of ticks and one cross, and the error is inside a per-job log that is mostly setup noise. Triage should not cost three round-trips before it starts — and for a verify job the log tail is the findings block, with its X_* codes and executable fix: lines already in it.

Working implementations: scripts/dev/shot.ts, scripts/gh/.

Context: docs/framework/ultimate-gaps.md §8.

[sebyx07]

Bun.WebView is a direct hit on x shot, with no Playwright and no npm install. Available since Bun 1.3.12.

The whole feature is five awaits:

await using wv = new Bun.WebView({ width, height, headless: true, console: onMessage });
await wv.navigate(url);                                   // a scratch-port `x dev`
const islands = await wv.evaluate<number>('...');          // mounted-island count
await wv.screenshot({ encoding: 'buffer', format: 'png' }); // shot.png

The console: option takes a callback and hands you every console message — which is this issue's verdict.json "console errors" half, and the part it correctly argues matters as much as the picture: a PNG cannot tell you the island threw.

macOS drives system WebKit with nothing installed; Linux and Windows drive an installed Chrome/Chromium/Edge — which is exactly why this issue is right that x shot must never be a verify step.

A second, larger prize. @ultimat3/scraping hand-rolls the entire CDP transport:

File	LOC
cdp-target.ts	347
page-over-target.ts	218
driver-cdp.ts	203
actionability.ts	106
page.ts	103
cdp-port.ts	75
cdp-snapshot.ts	63
total	~1,115

Bun.WebView owns launch, target lifecycle and trusted input, and its .cdp(method, params) escape hatch keeps Fetch.enable / Network.setBlockedURLs reachable for block: and intercept.ts.

Honest caveat: that escape hatch is Chrome-only, not WebKit — so a WebView driver is not a complete swap. And it must replace driver-cdp.ts at the existing Driver seam, never sit beside it, or the framework has bought a second path (axiom 1).

Also worth noting: RouteStats.lcpMs (budgets.ts:22) is declared and "written by nothing" today. Bun.WebView could make it a real measurement — outside the gate.