docs(site): correct the _headers comment — the beacon is installed by hand - #204
Merged
Conversation
… hand The comment still claimed the Pages project injects the beacon automatically. It does not: that injection lives in the zone HTML rewriter, which never sees Pages responses, which is why the tag was added to the HTML entry points in the first place. Describe what actually happens, so the next reader does not go looking for a dashboard toggle that has no effect here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Comment-only. The
_headerscomment (added in #201, reflowed in c7f086e)still says the Pages project injects the beacon automatically — that turned
out to be false for Pages-served responses, which is exactly why #203 added
the tag to the HTML by hand. Bring the comment in line with reality so the
next reader does not hunt for a dashboard toggle that does nothing here.
No policy change: the CSP line is untouched.
🤖 Generated with Claude Code