feat(seo): add AI agent Discord integration guide

[lilyshen0722]

Summary

• adds the crawlable Page 18 Discord integration guide with the approved manual-first rollout and event boundaries
• keeps credential examples as literal placeholders and adds approved internal plus reciprocal links
• updates route, static-render, hub-card, and SPA-route tests for 28 pages / 18 guides

Verification

• node --test scripts/generate-seo-pages.test.mjs
• npx jest --runInBand src/v2/tests/V2Login.test.tsx
• npm run typecheck
• npm run build
• npm test -- --watch=false
• generated Page 18 checked for canonical, sitemap, static-only shell, literal Discord placeholders, and no real runtime token

[lilyshen0722]

Gated at c00693ba. PASS on the Discord surface — every command and credential it names is real. Two sentences cite our documentation accurately, and the documentation is wrong in both cases.

Verified real, all of it: /commonly-summary, /discord-status, /discord-push, /discord-enable, /discord-disable all resolve to handlers in backend/services/discordService.ts (the switch at :809, the registration block at :854, the command list at :1042). DISCORD_BOT_TOKEN is consumed throughout. No token-shaped strings render — I checked the output for both cm_agent_ and Discord bot-token shapes and got neither.

Finding 1 — integration.event recurs here, and this is the propagation path.

"Commonly's agent event reference includes integration.event for external integration events, with source and data in the payload; its example uses source: "discord"."

That sentence is true as written. docs-site/agents/events.mdx:89 does include it, and its example does use source: "discord". But no code in this repository emits integration.event — the real type is integration.summary (backend/services/agentEventService.ts:351). I filed this as #1391 after #1388 shipped it, and predicted there that the docs-site/ source would re-seed it. This is that recurrence, one PR later.

Ordering consequence worth naming: because the sentence is phrased as a claim about the reference rather than about the runtime, fixing #1391 upstream will make this sentence false. So this guide is coupled to that fix — it is not independent of it.

Finding 2 — DISCORD_GUILD_ID is read by nothing.

"The documented deployment variables also include DISCORD_GUILD_ID for guild-specific commands where the operator needs it."

Also true as a statement about the docs (docs-site/deployment/environment-variables.mdx:60), and also naming something with no consumer. Zero hits in backend/ — control run with DISCORD_BOT_TOKEN on the same query returns hits, so the instrument works. It is wired in k8s/helm/.../backend-deployment.yaml:247 and read by no code.

The guild id is actually resolved from the Integration record, not from the environment — discordService.ts:240:

const guildId =
  integration.platformIntegration?.serverId ||
  integration.config?.serverId;

and the command deployer requires only two variables — deploy-discord-commands.js:51: const required = ["DISCORD_CLIENT_ID", "DISCORD_BOT_TOKEN"];. So an operator following this line will set a variable that does nothing, and may believe guild scoping is env-configured when it is per-integration data.

The pattern across both findings is the same and it is not the author's error. Both sentences are carefully hedged as claims about our documentation, and both are accurate at that level. The defect is upstream: docs-site/ names two things the code does not implement, and a hedge that makes a sentence unfalsifiable also makes it uncorrectable — a reader cannot tell "documented and implemented" from "documented only."

Neither is blocking on its own; #1393 is not less accurate than the docs it cites. But shipping it adds a second crawlable page depending on a doc fix that is already filed and open.

Mechanical: rendered all 28 pages — 0 [object Object], 0 stray undefined. node --test scripts/generate-seo-pages.test.mjs 2/2 on Node 22. Base is current main (0 behind). Test & Coverage passes here; Service Tests (Tier 1 — real DBs) is the one still pending.