webviews: agent-pane gallery entries test opens each entry's own frame (base red)

Merged
TE
15d ago
+3-3

Base red: webviews' bun run check fails on feat-cmux-next at check:browser-lanes.

#23237 added webviews/test/gallery-agent-pane-entries.test.ts with gallery frames that load every entry (/gallery/frame.html?entry=… without entryPath). Around the same time, #23250 added the guard that refuses that. Each PR was green alone. Since #23264, the cmux-next fast gates run that check on every PR that touches webviews/ or scripts/cmux-next/, so all of them go red on it (#23315's cmux-next fast gates, job 119185294577).

The test now builds its frames with galleryFrame(entry, { variant }) and warms them with warmGalleryFrame(vite, entries, { browser }) from ./support/galleryFrame, like the tests #23250 narrowed. Each case loads its own entry's file, not about 2,300 modules.

Test

cd webviews && bun scripts/check-browser-test-lanes.ts
  • Red on the base cb1b575ecb19: two errors, test/gallery-agent-pane-entries.test.ts:81 and :90, "opens a gallery frame without entryPath".
  • Green on the head: "Browser test lane imports checked." The full bun run check in webviews/ passes too.

Observed / Not run

  • Observed: the guard, red then green, and bun run check on huge-blue.
  • Not run: the browser test itself. It runs only in CI or on a Freestyle VM (CMUX_BROWSER_TESTS=1); this PR's webview browser lane runs it.

Changelog

none

Agent session: huge-blue

🤖 Generated with Claude Code

Summary by cubic

Fixes the gallery agent-pane entries browser test so each case opens its own entry's frame, clearing the red bun run check on feat-cmux-next.

  • The test now builds frames via galleryFrame and warms them with warmGalleryFrame, matching the per-entry guard added in #23250.
  • Browser test lanes should pass again on the cmux-next fast gates.