fix(web): disable AI chat on the EU instance

[Makisuo]

Turns off Maple AI chat on the EU dashboard for now. One flag, aiChatEnabled = currentRegion !== "eu" in apps/web/src/lib/region.ts, gates every entry point:

• header "Ask Maple AI" button
• "Ask Maple AI" command palette action
• the C shortcut (the global chat sheet never mounts)
• the "fix with AI" action on a broken dashboard widget
• /chat, which now redirects to / (covers old notification deep links)

US is unchanged.

Not covered: the EU API still forwards /api/chat/* to its AI Worker, and the follow-up chat inside investigations still works. Both can be gated separately if needed.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Summary by CodeRabbit

• Availability
  • AI chat is now available only in supported regions. In regions where it isn’t enabled, the chat page, dashboard chat button, command-palette action, and AI-powered widget repair option are not available. Elsewhere, these features remain accessible as before.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: c51f5d03-e112-4490-971d-11b54d76701c

📥 Commits

Reviewing files that changed from the base of the PR and between e69ad03 and 352d4bc.

📒 Files selected for processing (6)

• apps/web/src/components/chat/global-chat-sheet.tsx
• apps/web/src/components/command-palette/command-palette.tsx
• apps/web/src/components/dashboard-builder/widgets/widget-actions-context.tsx
• apps/web/src/components/layout/dashboard-layout.tsx
• apps/web/src/lib/region.ts
• apps/web/src/routes/chat.tsx

 ____________________________________________________________________
< Never go full rewrite. You don't buy that? Ask Netscape Navigator. >
 --------------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[maple-review-bot]

Maple observability review: 96/100

Excellent · Observability looks complete · reviewed 352d4bc

Score	Critical	Warnings	Notes	Changes observable
96/100	0	0	2	2 of 3

PR #997 gates the AI chat feature off on the EU instance by hiding the chat entry points (header button, command palette action, global chat sheet, widget fix action) and redirecting /chat to / in the TanStack Router beforeLoad hook. The gating is a single client-side constant (aiChatEnabled in region.ts) and the change adds no observability at all: no client event, log, span, or metric is emitted when the feature is silently removed for EU users. All six hunks read; no unit the diff adds carries instrumentation, though the repo's existing web telemetry (web.vitals/web.performance) is unrelated to this feature's removal and needs no work here.

Findings

Severity	Check	Where	Finding
Note	MET-02	apps/web/src/lib/region.ts:27	Observability gap
Note	STAT-04	apps/web/src/routes/chat.tsx:33	Observability gap

What to change

Observability gap (apps/web/src/lib/region.ts:27)

The change removes a user-facing feature (AI chat) from the EU instance by hiding or redirecting every entry point, but adds no telemetry: no client event, log, span attribute or metric. maple-web reports web.vitals and web.performance metrics to Maple; nothing on this new flag will appear. Six months from now, if EU users report that AI chat vanished, there will be no way to see from telemetry when the gate shipped, which region applied it, or whether any users still hit /chat redirects and were dropped on /.

In the existing maple-web meter idiom (e.g. web.vitals.ratings_total), add a monotonic counter such as web.chat.gate_total with attribute {maple.region: currentRegion, chat.action: "redirect" | "hidden"} — or at minimum log a single client event at module load when aiChatEnabled is false, so the gate's activation is visible in EU telemetry.

Observability gap (apps/web/src/routes/chat.tsx:33)

The /chat beforeLoad redirect covers old notification deep links but produces no trace signal that the redirect happened — the span for the /chat navigation and the redirect outcome carry no distinguishing attribute, and no event is logged. If EU traffic still arrives on /chat (which the redirect implies it will), this traffic is invisible to Maple.

Inside the beforeLoad hook, emit a client event (maple.client.event = "chat.redirect", maple.region = currentRegion) using the existing telemetry helpers in apps/web/src/lib/services/common/telemetry.ts so EU deep-link traffic shows up as a visible, measurable event.

What was reviewed

Change	Kind	Observable	Evidence
aiChatEnabled flag (apps/web/src/lib/region.ts)	feature flag	yes	single constant + comment; see telemetry convention in apps/web/src/lib/services/common/telemetry.ts
/chat redirect gate (apps/web/src/routes/chat.tsx)	route gate	yes	TanStack Router beforeLoad redirect; all other entries are client-side UI gating
AI chat entry-point gating (header, palette, shortcut, sheet, widget fix)	feature removal	no	no new spans, logs, events or metrics added by this diff

_{Score: 100, minus 25 per critical finding, 10 per warning and 2 per note. Check ids refer to Maple's instrumentation audit. Updated on every push.}