chore: add report analytics - #8
Merged
Merged
Conversation
blimmer
force-pushed
the
feat/report-analytics
branch
from
May 25, 2026 17:05
b53e861 to
28fe32b
Compare
blimmer
marked this pull request as ready for review
May 25, 2026 17:06
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.
Summary
Adds report-view analytics for generated PatchWave HTML reports, including embedded analytics config, browser-side PostHog initialization, CTA/assumption events, and session replay support. The analytics contract is split so shared code remains SDK-free while the CLI PostHog implementation lives behind its own adapter.
Review focus
Please look closely at the browser analytics initialization: session replay is enabled intentionally, autocapture remains disabled, and embedded JSON/form inputs are blocked or masked.
Commits
28fe32b— add report analytics