[HugoGresse]

Summary

The Slack bot only helps with the event today. This adds an opt-in "Answer any question, even unrelated to OpenPlanner or this event" checkbox on the Slack settings page. When enabled, the assistant also acts as a general assistant in Slack (same model and OpenRouter key). When disabled, nothing changes: the system prompt is byte-for-byte the one shipped today, so existing Slack installs and the in-app chat behave exactly as before.

Changes

• src/types.ts — new Event.slackAnswerAnyQuestion?: boolean | null (shared with functions via the existing import).
• src/events/page/api/components/SlackAssistantOptions.tsx — new "Assistant behaviour" block with the checkbox, rendered inside SlackChatSection for both official and self-managed apps. The helper text names the cost exposure (any workspace member who can message the bot uses the event OpenRouter key) and that the scope is a model instruction, not a hard block.
• src/events/page/slack/EventSlack.tsx / SlackManualSetup.tsx / mapEventSettingsFormToMutateObject.ts — form schema, default value, persistence, and a single form-level Save button (the per-section one in the manual setup is gone).
• functions/src/api/routes/chat/chatAgent.ts — optional answerAnyQuestion boolean on runChatAgent; when true a scope paragraph is added to the system prompt, otherwise the prompt is unchanged.
• functions/src/api/routes/slack/slackChatHandler.ts — passes the event flag; long replies are no longer cut at Slack's text cap but continued in the thread (splitForSlack cuts at paragraph / line / word boundaries).
• functions/src/api/routes/chat/chatAgent.test.ts, slack.test.ts, slackFormat.test.ts — exact prompt assertions, flag → system prompt wiring through the Slack handler, splitting.

Screenshot

New "Assistant behaviour" block on the Slack settings page, checkbox ticked and saved (local emulator, throwaway event). Taken before the Save button moved to the bottom of the page; the block itself is unchanged apart from the helper text.

Test plan

• tsc --noEmit clean on both front and functions
• vitest (Node 24, as in .nvmrc): chat/ and slack/ suites green, 46 tests
• Toggle the checkbox on the Slack page, save, reload: value persists (checked on the Firestore emulator)
• Ask the bot an off-topic question with the box on / off
• Ask for a very long answer with the box on: reply continues in the thread instead of being cut

🤖 Generated with Claude Code

---

Note

Low Risk
Prompt and UI configuration only; no auth or data-model breaking changes, and in-app chat behaviour is unchanged when answerScope is omitted.

Overview
Adds an opt-in per-event setting so the Slack assistant can answer off-topic questions, while tightening the default Slack behaviour to event-only topics.

Organizers get a new Assistant behaviour checkbox on the Slack settings page (slackAnswerAnyQuestion), persisted on the event and wired through the Slack form. The shared chat agent gains optional answerScope (event | any) that injects scope instructions into the system prompt: Slack always passes a scope (event-only unless the flag is on); in-app chat omits it, so its prompt stays unchanged. When scope is event, the model is told to decline unrelated questions; when any, it may act as a general assistant while still using event tools only for event questions.

Unit tests cover the three buildSystemPrompt variants (no scope, event, any).

^{Reviewed by Cursor Bugbot for commit 0694f8a. Configure here.}

[github-actions]

Visit the preview URL for this PR (updated for commit cf6a332):

• https://conferencecenterr--pr297-slack-answer-any-que-bo7uqckj.web.app
• https://apiopenplanner--pr297-slack-answer-any-que-4atofsup.web.app
• https://serviceapi--pr297-slack-answer-any-que-we6j4hfb.web.app

_{(expires Wed, 04 Nov 2026 08:20:08 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 0c15c45ea5a4c54095387eacf30c3755c9260f22}