Repository navigation
Conversation
ERerGB
requested review from
dmmulroy,
irvinebroque and
kale-stew
as code owners
November 16, 2026 21:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Agents fetch example applies nullish fallback to a Promise, so unmatched requests never reach its intended 404 response. Split Tunnel migration guidance also says no API exists, and Turnstile handling conflates API credentials with challenge tokens.
This corrects those examples and separates domain onboarding from code-only work. Browser audits now distinguish one trace and accessibility-tree evidence from unverified global/visual behavior. Optional skill dependencies and index links have explicit discovery fallbacks; existing setup authorization and host-specific persistence are respected.
Validation: git diff --check and patch applicability passed. The routing and split-tunnel guidance was checked against official Cloudflare documentation; no live Cloudflare resources were mutated or deployment tests run.
References: