Skip to content

docs(lens): a refused Browser Run call says nothing about the engine #288

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
oddharsh merged 3 commits into from
Aug 9, 2026
Merged

docs(lens): a refused Browser Run call says nothing about the engine #288

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
30d55ef
docs(lens): a refused Browser Run call says nothing about the engine
oddharsh Aug 8, 2026
c0f39f7
chore: retrigger the code-scanning run
oddharsh Aug 8, 2026
1432114
Merge branch 'main' into docs/lens-engine-429-caveat
oddharsh Aug 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -944,6 +944,20 @@ generic hex back.
actually saw. The label is `kitesurf-requested` now, and the 400-retry is
unchanged.

**A NON-200 carries no engine information whatsoever, and on the free plan that
is the COMMON case rather than the edge.** `kitesurfParamLive` only flips true
on `response.ok`, so a call the API refuses falls through to `chromium-rest`
regardless of whether the selector was honoured, and the span records that
label beside the failure. Since the daily browser-minute ceiling is what
usually does the refusing, a log window can fill with `chromium-rest` while
containing zero evidence about Kitesurf either way. Measured 2026-08-08:
filtering Workers Logs on `exists(lens.render_engine)` returned five
`lens.browser` spans over 24h, every one of them `chromium-rest` with
`lens.outcome: browser_budget_spent`, reaching back to a 2026-08-07 scan of
theverge.com on an earlier version. Read `lens.render_engine` only alongside
`lens.outcome`, and treat a window with no successful render as NO DATA rather
than as a verdict for Chromium.

**Promoting it takes one control: does the endpoint REJECT an invented engine
name?** `npm run kitesurf:check` runs that control and prints a verdict — same
shape as the `--x-bogus-flag` control on wrangler and
Expand Down
Loading