Skip to content

Use canonical product key for browser logs - #15

Merged
sarthakagrawal927 merged 1 commit into
mainfrom
fix/canonical-browser-log-attribution
Oct 2, 2026
Merged

sarthakagrawal927 merged 1 commit into
mainfrom
fix/canonical-browser-log-attribution

Conversation

@sarthakagrawal927

Copy link
Copy Markdown
Member

Change

Replace only the browser logger public-key literal with the already configured pageview tracker key, verified as active production for this canonical catalog project, workspace and exact origin. No event behavior or endpoint changes. Existing historical logs remain intact.

Verification

  • Bounded read-only production scope query passed with zero rows written.
  • node --check apps/hub/public/app-health-log.js passed.
  • git diff --check passed.
  • Root reviewed the one-line diff; exact-head CI is required before merge.
  • Guarded release and live byte/source verification follow merge.

Closes #14

Keep App Health issue 96 open for end-to-end report qualification.

@sarthakagrawal927
sarthakagrawal927 merged commit 8d0c8b9 into main Oct 2, 2026
1 check passed
@sarthakagrawal927
sarthakagrawal927 deleted the fix/canonical-browser-log-attribution branch October 8, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Repair canonical browser log attribution

1 participant