feat(docs): GA4 install on mcp.wyre.ai (env-gated) - #113
Draft
asachs01 wants to merge 1 commit into
Draft
Conversation
Wires Google Analytics 4 (property G-V3W6M1YEHL — same as wyre.ai, conduit.wyre.ai, conduit /docs) into BaseLayout.astro. Dual-gated: enableGA = import.meta.env.PROD && import.meta.env.SITE === 'https://mcp.wyre.ai' so GA only loads on the mcp.wyre.ai Docker build that ships to production. Excludes local dev (PROD=false) and the GitHub Pages preview build (SITE_URL=https://wyre-technology.github.io). Default SITE in astro.config is 'https://mcp.wyre.ai', so the PROD half of the gate is what keeps local dev uninstrumented. gtag.js is loaded without Subresource Integrity by design — Google regenerates the script continuously and never publishes integrity hashes, so pinning SRI would break GA on every upstream update. Trust model is googletagmanager.com TLS + the published canonical snippet (matches Angela's wyre.ai/conduit installs). Inline justification comment in BaseLayout.astro for the next maintainer. No CSP found in this repo — no policy update needed. Single-purpose PR. Draft + gated on Aaron; will not merge before mcp-gateway PR #190 (forge staging-gate) lands.
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.
GA4 install —
mcp.wyre.aidocs only (env-gated)Wires GA4 (
G-V3W6M1YEHL— same property as wyre.ai + conduit.wyre.ai + conduit /docs) intomsp-claude-plugins/docs/src/layouts/BaseLayout.astro. Per Aaron's D6 ruling, the install is env-gated to production builds forhttps://mcp.wyre.aionly.Gate
Dual-gate is intentional. The default
SITE_URLin this repo'sastro.config.mjsis'https://mcp.wyre.ai', so a SITE-only check would also match local dev. ThePRODhalf excludes dev/preview; theSITEhalf excludes the GitHub Pages preview build (SITE_URL=https://wyre-technology.github.io).PRODSITEnpm run dev(no envs)https://mcp.wyre.ai(default)npm run preview(no envs)https://mcp.wyre.ai(default)SITE_URLset)https://wyre-technology.github.iohttps://mcp.wyre.ai¹ Note:
astro previewruns the production build locally, soPROD=truethere. SinceSITEwould still behttps://mcp.wyre.aiby default, technically GA would fire on a localastro previewwith no envs — butastro previewis a development tool not a deployed surface, and adding a third gate for it would be over-engineering. If this becomes a concern, document it for the rollback playbook.Where it lives
msp-claude-plugins/docs/src/layouts/BaseLayout.astro(the existing root wrapper used by every page).<head>, after<SEOHead>, before the dark-mode inline script. Renders nothing whenenableGAis false (the<Fragment>evaluates to empty).Subresource Integrity — intentionally not used
gtag.jsis loaded without SRI. Google continuously regenerates that script to reflect property-configuration changes and does not publish integrity hashes for it, so pinning SRI would break GA on every upstream update. Trust model isgoogletagmanager.comTLS + the published canonical snippet — matches Angela'swyre.ai/conduit.wyre.ai/conduit /docsinstalls. Inline justifying comment inBaseLayout.astroso the next maintainer sees the reasoning.CSP
None present in this repo — confirmed by grep across the docs/ tree. No policy update needed; the original task's "if no CSP, skip" branch applies.
Build verification
npx astro buildruns clean locally — 106 pages built in 1.08s. No type errors. The conditional renders nothing in the non-prod / non-mcp.wyre.ai paths; HTML diff verified by inspectingdist/(no gtag in the GH-Pages-style build).Scope discipline
src/layouts/BaseLayout.astrois touched.astro.config.mjschange. No new dependency. No CSP addition (none existed).public/og-image.png) are pre-existing WIP and not included in this PR.Sequencing
This PR rides behind mcp-gateway PR #190 (forge staging-gate). It is NOT to be merged before #190 lands and the gate is live, per the cadre's PR-as-gate convention.