hive.slack-notifications-setup

1# Slack Notifications Setup (Sentinel)
2 
3Sentinel pings the user on Slack when a colony stalls and lets them reply from
4Slack to keep it going. It needs a Slack app with two tokens:
5 
6- a **Bot User OAuth Token** (`xoxb-…`) — stored under credential id `slack`, used to *send* alerts and call the Slack API.
7- an **App-Level Token** (`xapp-…`) with `connections:write` — stored under credential id `slack_app`, used by Socket Mode to *receive* the user's reply.
8 
9You do the whole thing end to end: reuse-or-create the app, read the tokens, store
10them with the **`sentinel_setup`** tool (the same API the desktop connector uses),
11create/select the channel **via the Slack API**, and turn Sentinel on — without
12making the user paste anything.
13 
14**Activate `hive.browser-automation` first** — this skill assumes you know the
15lifecycle rules (the bridge attaches to the user's own Chrome; never launch or kill
16a browser), the screenshot + viewport-fraction coordinate workflow, and
17`hive-browser interact`.
18 
19## Before you start — check what already exists
20 
211. Run `sentinel_setup({"action": "status"})`. If it shows **both** `slack bot` and
22   `slack app` already configured, the app and tokens are already in place — skip
23   Steps 1–4 entirely and go to **Step 5 (channel)**. Don't recreate anything.
242. Confirm the user is signed into the right Slack workspace: run
25   `hive-browser navigate https://api.slack.com/apps --json` in the terminal. If it shows a sign-in screen,
26…