Evan JarrettandClaude Opus 5 34b4516aa7 test/e2e: correct the claim that headed Chromium cannot launch here ...

It can, and normally in well under a second. Two launches hung for the full
180s handshake timeout under heavy concurrent docker and test load, and I wrote
that up as "headed is impossible from an agent shell" and moved everything to
headless. That was wrong, and wrong in a way that would have quietly degraded
every future browser check.

The display is reachable: DISPLAY=:0, XAUTHORITY set to the mutter XWayland
cookie, both the Wayland socket and /tmp/.X11-unix/X0 present, xdpyinfo happy.
The README now says to check xdpyinfo and retry rather than conclude anything,
and batch10-anonpull.mjs defaults to headed again.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SeaUS5AFPX9gqCahoLRMRh

2026-08-25 16:34:25 -05:00

..

e2e

test/e2e: correct the claim that headed Chromium cannot launch here

2026-08-25 16:34:25 -05:00

integration

test: cover the nested-repo tag rkey on the delete paths

2026-08-25 16:34:25 -05:00

stripe-integration

billing: make Stripe webhook delivery idempotent and retryable

2026-08-09 21:14:58 -05:00