Add AnalyticLunch plugin entry

[dandyer]

What this adds

AnalyticLunch (plugin) — website traffic tracking plus pay-per-report SEO and competitive intelligence, with an MCP server on npm (analyticlunch-mcp).

Checklist

• This PR adds exactly ONE new file under content/ (plus assets for this entry, if any).
• It follows CONTRIBUTING.md — required fields + the golden rules (G1–G8).
• npm run validate passes locally (schema, slug, vocabularies).
• slug is kebab-case and exactly matches the filename.
• I ran / used this myself end to end — it works today.
• Every URL in the frontmatter resolves to real, relevant content.
• The prompt body is the real, complete prompt — not a summary or a teaser.
• The entry body is plain markdown — no raw HTML.
• I did NOT set verified_at or status: live.
• This is not an ad.
• If this is someone else's work — n/a, this is my own product, submitted as author.
• I license this contribution under CC BY 4.0.

Where it came from

First-party listing — I build AnalyticLunch and run it against my own sites. Flagging that openly, same as my Jobkeepr PR, since self-submissions deserve extra scrutiny under G6.

Verifiable now:

• npm: https://www.npmjs.com/package/analyticlunch-mcp (v1.0.0)
• API: GET https://analyticlunch.com/api/traffic/sites returns 401 without a key, authenticates on the x-api-key header
• Pricing: https://analyticlunch.com/pricing

One caveat I want to state up front rather than bury: MCP/API access is gated behind an active subscription. A free account can create reports but cannot mint an API key — the endpoint returns 402. Traffic tracking is $6/mo or $15/yr per site, which is the cheapest path to a key. Step 3 of the install steps says this explicitly so nobody follows the entry and hits a wall at the key step. If a paywalled setup path disqualifies an entry here, close this and no hard feelings.

The part that isn't just another analytics connector is get_weekly_report — competitive intelligence on the competitors you're tracking, in the same conversation as your own traffic numbers. "Traffic dipped last week" and "here's who started outranking you" become one question instead of two tools.

The prompt makes the bot name the site and exact date range behind every number it quotes, say plainly when a window is too thin to read a trend from, and refuse to pin a traffic change on a cause the data doesn't support. Creating a tracking link is the only write, and it shows the destination and full UTM string before it commits.

🤖 Generated with Claude Code

https://claude.ai/code/session_012vGCK6nR6qveaEpizNJ1qD

[dandyer]

Pushed a fix and rebased onto current main. build and links now pass.

The original failure was mine: pricing_note was 205 chars against the schema cap of 120 (src/content.config.ts:30). Worth flagging for other contributors that npm run validate does not catch this one. It only surfaces at astro sync during build, so a local npm run validate can pass on an entry that CI rejects.

The two checks still red are not from this PR:

• validate fails on no raw colour literals outside tokens.css (§4.1.1), pointing at src/components/ConnectCallout.astro:74 and src/components/SiteHeader.astro:435. Both are on main right now and the last five main runs are red for the same reason, including the Jobkeepr merge (e8d837e). The ConnectCallout hit looks like a false positive: the literal is inside a CSS comment explaining what --color-surface resolves to. Left both alone since this PR should be one file under content/.
• gate wants the community label and a maintainer approval against the head SHA. Maintainer-side.

Also flagging the honest weak spot again so it is not buried: API access here needs a paid plan, so a reader cannot try this one for free. Install step 3 says so outright. Fine by me if that disqualifies it.

[scheemunai]

Merged into main (commit d8ae584) and live now: https://grokbot.dev/plugins/analyticlunch/

Thanks — this was a clean, honest submission and it reviewed fast. I checked it against the shipped package rather than taking the write-up's word for it: analyticlunch-mcp@1.0.0 is published, and all five capabilities the entry claims map to real tools in dist/ (list_traffic_sites, get_traffic_summary, create_tracking_link, list_tracking_links, get_weekly_report). Nothing invented. analyticlunch.com and /pricing both 200.

Two things I'll call out approvingly, because they're the parts submissions usually get wrong:

• The install steps say out loud that API access is gated on an active subscription and that a free-only account gets a 402. Being upfront about the paywall is worth more here than a softer pitch.
• The prompt puts the one write in the toolset (create_tracking_link) behind an explicit confirmation, and tells the bot to name the site and date range behind every number and to refuse to narrate a thin window as a trend. That's exactly the shape we want on anything that touches state.

Maintainer edits applied on merge — these two are reviewer-set, so they're never something a submitter should fill in:

• status: proposed → status: live
• added verified_at: "2026-09-04T05:01:16Z"

No other changes; your schema was already valid (tagline 83/90, pricing_note 117/120, marketing/analytics a real category pair). Full build gate green before promote.

One optional follow-up if you want it: works_with is currently empty. If AnalyticLunch pairs with anything in src/data/integrations.json, adding those canonical names would surface the page on those integration lanes too. Happy to take a one-line PR for that.