fix(onboarding): ask where incidents are discussed

[coreplane-switchboard]

The Slack public-channel picker now asks where incidents are triaged and discussed on its first prompt. This makes the existing onboarding question actionable without changing channel selection behavior.

polylanedotcom#397 needs onboarding to identify the channels where incident work happens. Keeping that question in the CLI picker puts it at the decision point while preserving the established Slack integration flow.

Rendered by the plan runner from the coding run's submitted description; the run ended before it could open the pull request itself.

[coreplane-switchboard]

LGTM: The exact initial Slack channel prompt is updated while the selected-state wording and surrounding flow remain unchanged and regression-covered.

Note

Approved · head cddb40f · no findings

Full review

No findings; the exact initial prompt is updated and the repeated-selection behavior remains regression-covered.

[github-actions]

Auto-approved: coreplane-switchboard[bot] reviewed this PR and posted an LGTM verdict (see its review). A repo admin enabled this via the auto-approve workflow.

[justinhelmer]

Shipment receipt — September 23, 2026: reviewed head cddb40f05e1fd78055a2e23852692477b8fadf5d merged at 2:59:52 PM PDT as 4175743da2c6791e35bfb07518f2fdf7bc8a9f61. Release v0.2.42 at 84e4767a980f2e6fd2907a732894a4e5b967de00 passed its Node 20/22/24 release checks, npm publication, GitHub release and Homebrew update in release workflow. Real production-installer smoke passed at 3:02:03 PM PDT: both normal GitHub digest verification and blocked-GitHub/checksums.txt fallback installed 0.2.42 with sha256 verified. Raw logs show the expected noninteractive sign-in stop; this proves distribution/installability, not authenticated onboarding or Slack picker rendering. Actual setup→CLI rendering and screenshot evidence remain with the existing website #397 validation lane.