chore(docs): remove shrill.en.dev analytics script

[jdx]

Removes the proxied shrill.en.dev analytics snippet from the VitePress docs config — the endpoint is going away.

---

Note

Low Risk
Low risk documentation-site change; it only removes a third-party analytics script include and should not affect core functionality beyond stopping analytics events.

Overview
Removes the shrill.en.dev analytics <script> (and its data-domain/data-api attributes) from the VitePress head config for the docs site, leaving only the existing OpenGraph/Twitter meta tags.

^{Reviewed by Cursor Bugbot for commit 52c5f7e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

Removes the proxied analytics <script> tag (pointing to shrill.en.dev) from the VitePress head config since the endpoint is being decommissioned. No functional or behavioural changes beyond the analytics collection stopping.

Confidence Score: 5/5

Safe to merge — trivial one-line removal with no side effects.

Single-element removal from a static config array; no logic, no imports, no tests affected. No issues found.

No files require special attention.

Important Files Changed

Filename	Overview
docs/.vitepress/config.mts	Removes the defunct shrill.en.dev analytics script element from the VitePress head array; no logic changes.

Sequence Diagram

sequenceDiagram
    participant Browser
    participant DocsPage as usage.jdx.dev
    participant Analytics as shrill.en.dev (removed)

    Note over Browser, Analytics: Before this PR
    Browser->>DocsPage: Load page
    DocsPage-->>Browser: HTML (includes analytics script tag)
    Browser->>Analytics: POST /f5f1/event (pageview)
    Analytics-->>Browser: 200 OK

    Note over Browser, Analytics: After this PR
    Browser->>DocsPage: Load page
    DocsPage-->>Browser: HTML (no analytics script tag)

Loading

_{Reviews (1): Last reviewed commit: "chore(docs): remove shrill.en.dev analyt..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.03%. Comparing base (cae041f) to head (52c5f7e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #614   +/-   ##
=======================================
  Coverage   79.03%   79.03%           
=======================================
  Files          48       48           
  Lines        7235     7235           
  Branches     7235     7235           
=======================================
  Hits         5718     5718           
  Misses       1140     1140           
  Partials      377      377           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gemini-code-assist]

Code Review

This pull request removes a script tag and a meta tag from the VitePress configuration. A suggestion was made to include a trailing comma on the final array element to minimize future diff noise and align with TypeScript style conventions.

[gemini-code-assist]

It is recommended to maintain the trailing comma for the last element in the array when it is followed by a newline. This practice improves maintainability by reducing diff noise in future changes and adheres to common TypeScript style guides, such as the Google TypeScript Style Guide.

    ["meta", { name: "twitter:image", content: "https://usage.jdx.dev/android-chrome-512x512.png" }],

References

1. The Google TypeScript Style Guide recommends using trailing commas in container literals (such as object literals and array literals) whenever there is a line break between the final element and the closing bracket to minimize diff noise. ^(link)