[ntdat812]

Summary

tests/unit/claude-web-transport.test.ts checks that the Claude Web executor carries no
execution-time dependency on the standalone Turnstile solver. Two of its assertions are
anchors — there to prove the file read resolved to the real barrel, so the negative guards
below them cannot pass against a moved or emptied file. They were pinned to the exact
construction spelling:

assert.match(indexSource, /"claude-web": new ClaudeWebExecutor\(\)/);
assert.match(indexSource, /"cw-web": new ClaudeWebExecutor\(\)/);

#11421 made the executor barrel lazy. The values are now
() => import("./claude-web.ts").then((m) => new m.ClaudeWebExecutor()), so neither anchor
matches any more. The wiring they guard did not change — only how the map constructs executors.

This is a base-red gate. The test fails on release/v3.8.51 itself, so every open PR
inherits the failure in Unit Tests fast-path (1/4) no matter what it touches.

The anchors now match the alias key and the class name and let the construction between them be
spelled either way:

assert.match(indexSource, /"claude-web":.*ClaudeWebExecutor/);
assert.match(indexSource, /"cw-web":.*ClaudeWebExecutor/);

. does not match a newline without the s flag, so each stays confined to its own entry.

Related Issues

• Refs perf(executors): lazy-load the executor registry — defer class imports + construction to first use (#11220) #11421 (the lazy-executor change this anchor was not updated for)

Validation

• Change type: other (test-only)
• Focused tests and category gates from the golden path
• npm run lint — clean (eslint exit 0)
• Reconciled with the current active release base — branched from origin/release/v3.8.51
  at 6eb7bf0ba9
• Production-code changes include a new or updated automated test in this PR — n/a, no
  production code changed

# on 6eb7bf0ba9, unmodified
$ node --test tests/unit/claude-web-transport.test.ts
# tests 9 / pass 8 / fail 1     <- not ok 2, "Claude Web executor transport orchestration"

# with this change
# tests 9 / pass 9 / fail 0

The loosened anchor still catches a real break. A looser assertion is only worth having if
it still fails when the thing it guards is actually gone, so I checked that rather than assuming
it: repointing one alias at a different executor —

-  "cw-web": () => import("./claude-web.ts").then((m) => new m.ClaudeWebExecutor()), // Alias
+  "cw-web": () => import("./default.ts").then((m) => new m.DefaultExecutor()), // Alias

— turns the test red again (pass 8 / fail 1), and restoring it turns it green. The guarantee is
unchanged; only the spelling it tolerates is wider.

Tests Added Or Updated

• tests/unit/claude-web-transport.test.ts — two anchor assertions relaxed. No production code
  changed.

Coverage Notes

No src/, open-sse/, electron/ or bin/ change, so coverage is unmoved.

Reviewer Notes

• I checked whether the same stale pattern exists elsewhere before scoping this:
  grep -rn '": new [A-Za-z]*Executor' tests/ returns these two lines and nothing else, so this
  is the whole of that class of breakage, not the first of many.
• The alternative fix is to re-pin the anchors to the new lazy spelling. I did not, because that
  reproduces the original problem — the next change to how the barrel constructs executors would
  turn this test red again for a reason that has nothing to do with Turnstile. What the test
  cares about is which class the alias resolves to, and that is what it now asserts.
• Worth saying plainly: I found this because it was failing CI on two unrelated PRs of mine
  (fix(cache): compare expires_at against an ISO cutoff, not datetime('now') (#11559) #11579, fix(api): restore the background-refresh injection point on /v1/models (#11551) #11581) alongside chore(stryker): register the two test files covering three mutated modules #11577 and test(authz): pin the GET-exemption set by membership, not by count (#11531) #11580 by other authors. It is not something I broke,
  and it is not specific to my changes.

[ntdat812]

CI on this PR is red, and I do not think any of it is mine. Recording the check rather than
leaving it to be re-derived.

The same six gates fail — Docs Gates (fast-path), Fast Quality Gates,
No new ESLint warnings, and three of the four Unit Tests fast-path shards — on every open
pull request against release/v3.8.51 that I can see, including #11577, #11580 and #11582,
which are not mine and touch entirely different files. The failing unit tests
(db-cleanup, db-settings-crud, cursor-renewal, kiro-multi-account-isolation,
openrouter-provider-stats, namespace-tool-identity-integration,
t31-t33-t34-t38-model-specs, authz/route-guard-version-get-exemption) have no overlap with
this diff.

Locally, at the base commit this branch is rebased onto (6eb7bf0ba9), the focused tests for
this change pass and the before/after evidence in the description reproduces.

Happy to rebase again whenever the base is green — it has moved 45 commits since I opened this,
so I would rather rebase once against a known-good tip than keep chasing it. Related: #9282.