docs(analytics): record assistant review cadence and script hardening

[GigaHierz]

Refs #2307, Refs #2302

What changed

• assistant.js: script.crossOrigin = 'anonymous'. Checked first: curl -sI -H 'Origin: https://docs.celo.org' https://docs-assistant.celo.org/widget.js returns access-control-allow-origin: *, so the CORS load works (without that header the widget would fail to load). The header comes from the /widget.js headers rule in docs-ai-assistant's next.config.ts, which ANALYTICS.md now names.
• ANALYTICS.md:
  • Review policy (task: make the assistant's existing telemetry reportable (GA4 custom dimensions, gtag after GTM swap, unanswered-question review) #2307 AC 3): the owned task is @celo-org/devrel triaging the weekly "Docs assistant: N unanswered questions" issue and closing it once its real gaps are doc issues. The Redis list docs-assistant:questions stays as the raw store for digging deeper. Replaces the monthly Redis review.
  • The weekly report is described accurately: probes are shown as a count with a short sample.
  • The raw-question rule is scoped to manual copies. The doc states plainly that the weekly bot report currently pastes raw questions into a public issue, and that redacting it, skipping refused: true entries and expiring the Redis log is tracked in docs-ai-assistant issue Convert the validator-guide to docusaurus. #3.
  • Post-swap verification (task: make the assistant's existing telemetry reportable (GA4 custom dimensions, gtag after GTM swap, unanswered-question review) #2307 AC 2): the pass criterion is one assistant_question event in GA4 Realtime with answered populated. The typeof window.gtag check is dropped, since a hand-defined shim sends no hit and passing it proves nothing under GTM. The task: make the assistant's existing telemetry reportable (GA4 custom dimensions, gtag after GTM swap, unanswered-question review) #2307 body uses the same wording.
  • A "Script hardening" section recording that no SRI and no CSP are in place and why (task: harden the third-party script path for the docs assistant (no SRI, no crossorigin, no CSP) #2302 ACs 1, 2, 5).

Boxes still open

• task: make the assistant's existing telemetry reportable (GA4 custom dimensions, gtag after GTM swap, unanswered-question review) #2307 AC 1 (GA4 custom dimensions) and the Realtime check: need GA4 admin and the GTM swap (feat(analytics): instrument the add-network conversion and document how the site is measured #2300); not claimed here.
• task: harden the third-party script path for the docs assistant (no SRI, no crossorigin, no CSP) #2302 AC 3/4: SRI not adopted (breaks on widget deploys); CSP depends on Mintlify plan support, not confirmed.

Verification

$ node --check assistant.js   # ok
$ mint broken-links
success no broken links found

🤖 Generated with Claude Code

[palango]

The crossOrigin change looks good. widget.js returns access-control-allow-origin: *, and docs-ai-assistant's next.config.ts sets it on purpose, so it won't vanish by accident. A few lines in the new ANALYTICS.md text don't match what the weekly report does, and since ANALYTICS.md is served publicly at docs.celo.org/ANALYTICS, I'd fix those before merge.

The main one is the rule against pasting raw questions into issues. The weekly report bot pastes up to 25 raw questions into a public issue every Monday (see #2343, which also includes an injection prompt the probe filter missed). The doc and the bot need to agree: either raw text in bot-filed issues is acceptable and the rule should say so, or the report should change. Details inline.

Separately, four weekly issues (#2314, #2320, #2324, #2343) are still open. The weekly issue already filters to answered: false, so a monthly Redis read mostly repeats it. It may be simpler to make triaging those issues the owned task. Also, the report doesn't skip refused: true entries, so off-topic refusals show up in the weekly gaps list. That's a fix for the assistant repo, not this PR.

[palango]

The report does list some probes: route.ts passes probeClusters.slice(0, 3) (first 60 chars each) into a "Sampled rather than listed in full" block, and #2343 shows three. Suggest "with injection and enumeration probes counted and only a short sample shown".

[palango]

This conflicts with the weekly report two lines up, which pastes up to 25 raw questions into a public issue (#2314, #2320, #2324, #2343). Which one is the policy? If bot-filed issues are fine, scope this rule to manual copies. If not, the report needs changing in docs-ai-assistant, and this PR should point to that follow-up.

[palango]

Optional: name where the header comes from (docs-ai-assistant next.config.ts, the /widget.js headers rule), so whoever edits that file knows docs.celo.org now depends on it.

[palango]

The bullet above says a hand-defined gtag shim sends no hit, so typeof window.gtag === 'function' passing doesn't show anything reaches GA4. Under GTM alone it's undefined, and widget.js still only tracks through window.gtag. I'd drop the gtag clause and keep the Realtime assistant_question event as the pass criterion. #2307 AC 2 still has the old gtag wording and needs the same update.

[GigaHierz]

Review points addressed in edca066 (only ANALYTICS.md changed; assistant.js is as before):

• Weekly report: now says probes are counted and only a short sample is shown.
• Policy: the owned task is triaging each weekly "Docs assistant: N unanswered questions" issue (owner @celo-org/devrel), closing it once its real gaps are doc issues. The monthly Redis read is gone; the Redis list stays as the raw store.
• Raw-question rule: scoped to manual copies. The doc now states that the bot report currently pastes raw questions into a public issue, and that redacting it, skipping refused: true entries and expiring the log is tracked in celo-org/docs-ai-assistant#3.
• Header source: names the /widget.js headers rule in docs-ai-assistant's next.config.ts (checked that it sets Access-Control-Allow-Origin: *).
• gtag: the typeof window.gtag clause is dropped; the pass criterion is one assistant_question event in GA4 Realtime. task: make the assistant's existing telemetry reportable (GA4 custom dimensions, gtag after GTM swap, unanswered-question review) #2307 acceptance criterion 2 and its "monthly pull" line were updated to match.

mint broken-links passes.

[palango]

Thanks, this covers everything from my last review. The probe wording matches what route.ts does now, the raw-question rule is scoped to manual copies and points at docs-ai-assistant#3, and making triage of the weekly issue the owned task is simpler than a monthly Redis read. I checked the /widget.js rule in next.config.ts and the live header, and the post-swap check no longer leans on window.gtag.

Two optional nits inline. One more, outside this PR: the Gap 2 paragraph in #2307 still says GTM's Google tag should define window.gtag, which contradicts what ANALYTICS.md now says. Worth fixing so the issue and the doc agree.

[palango]

Nit: this page is public, and on docs.celo.org "issue #3" renders as plain text with no repo. Could you use the full URL (https://github.com/celo-org/docs-ai-assistant/issues/3)?

[palango]

Nit: the comment in docs-ai-assistant's next.config.ts says Mintlify exposes no header configuration on any plan, and that a <meta> CSP injected by our loader would apply to nothing. This line hedges to the Starter plan. Whichever is accurate, the two should agree.