adam/orchestrator
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
This repository has been archived on 2026-08-04. You can view files and clone it, but cannot push or open issues or pull requests.
orchestrator/agent-team/slack/agent-team-manifest.json

51 lines
1.1 KiB
JSON
Raw Normal View History

fix(agent-team): repair Slack listener block_actions matcher; add dedicated Slack app (#25) The Socket Mode inbound listener crashed at registration time on first live run: `@app.action({})` raised `BoltError: action ({}) must be any of str, Pattern, and dict` under slack_bolt 1.28.0, killing the listener thread (the whole inbound answer path — message/app_mention/block_actions — went down, caught only by the coordinator's respawn watchdog). serve() is marked `# pragma: no cover - live socket`, so this was never exercised until the R720 bring-up. Replace the unsupported empty-dict matcher with a catch-all `re.compile(r".*")` action_id regex; handle_event still does the real filtering + AUTHZ-01 owner-allowlist gate, so over-matching is safe. Verified on sh-secrev: listener connects (live Socket Mode WebSocket), outbound chat.postMessage works, 0 errors. /sh-security-review PASS (no confirmed critical/high; matcher change introduces no new findings). Also adds the dedicated Slack app (manifest + README) backing the clarifier gate — "Sea Haven agent-team" (A0BC7AT8NUD), workspace-scoped install to avoid the Enterprise-Grid `scope_not_allowed_on_enterprise` org-install trap — and patches the provisioning runbook's stale langgraph pin (1.1.10 -> 1.2.5).
2026-06-22 13:16:35 -04:00
{
"display_information": {
"name": "Sea Haven agent-team",
"description": "Human-gated clarifier for the R720 agent-team SDLC pipeline (Plane-2 coordinator).",
"background_color": "#0c4f6f"
},
"features": {
"bot_user": {
"display_name": "agent-team",
"always_online": true
fix(ws2): register /new-task slash command + commands scope in Slack manifest The slack_listener handles {type:slash_commands, command:/new-task} but the app manifest declared no slash commands and no 'commands' scope, so Slack never offered /new-task (the command can't be invoked). Add the slash command + commands bot scope. Socket Mode delivers it over the socket (no request URL). APPLY: update the app A0BCC7TTU66 from this manifest + reinstall to pick up the new scope.
2026-06-23 13:20:08 -04:00
},
"slash_commands": [
{
"command": "/new-task",
"description": "Start a new agent-team task (clarify -> plan -> review)",
"usage_hint": "<task description>",
"should_escape": false
}
]
fix(agent-team): repair Slack listener block_actions matcher; add dedicated Slack app (#25) The Socket Mode inbound listener crashed at registration time on first live run: `@app.action({})` raised `BoltError: action ({}) must be any of str, Pattern, and dict` under slack_bolt 1.28.0, killing the listener thread (the whole inbound answer path — message/app_mention/block_actions — went down, caught only by the coordinator's respawn watchdog). serve() is marked `# pragma: no cover - live socket`, so this was never exercised until the R720 bring-up. Replace the unsupported empty-dict matcher with a catch-all `re.compile(r".*")` action_id regex; handle_event still does the real filtering + AUTHZ-01 owner-allowlist gate, so over-matching is safe. Verified on sh-secrev: listener connects (live Socket Mode WebSocket), outbound chat.postMessage works, 0 errors. /sh-security-review PASS (no confirmed critical/high; matcher change introduces no new findings). Also adds the dedicated Slack app (manifest + README) backing the clarifier gate — "Sea Haven agent-team" (A0BC7AT8NUD), workspace-scoped install to avoid the Enterprise-Grid `scope_not_allowed_on_enterprise` org-install trap — and patches the provisioning runbook's stale langgraph pin (1.1.10 -> 1.2.5).
2026-06-22 13:16:35 -04:00
},
"oauth_config": {
"scopes": {
"bot": [
"chat:write",
"channels:history",
"groups:history",
"im:history",
fix(ws2): register /new-task slash command + commands scope in Slack manifest The slack_listener handles {type:slash_commands, command:/new-task} but the app manifest declared no slash commands and no 'commands' scope, so Slack never offered /new-task (the command can't be invoked). Add the slash command + commands bot scope. Socket Mode delivers it over the socket (no request URL). APPLY: update the app A0BCC7TTU66 from this manifest + reinstall to pick up the new scope.
2026-06-23 13:20:08 -04:00
"app_mentions:read",
feat(agent-team): 👍-acknowledge received Slack answers (reactions:write) WS Slack-UX Feature 2. When the inbound listener acts on an answer in a task thread, it adds a 👍 reaction to that reply so the human sees the machine received it. - SlackListener gains an optional reactor seam; handle_event reacts to the inbound reply message (channel + event ts) AFTER the AUTHZ-01 owner check passes — a non-owner message is rejected and never reacted to. Best-effort: any reaction failure (notably a missing scope) is swallowed and never breaks handle_event or the listen loop. - /new-task is NOT reacted to (a slash command has no reactable message); its "📥 Task received" root post is the acknowledgement. - build_slack_reactor wraps WebClient.reactions_add(name="thumbsup"); the default listener factory wires it best-effort from SLACK_BOT_TOKEN. - Adds reactions:write to the bot scopes in agent-team-manifest.json. NOTE: the new reactions:write scope requires Adam to re-apply the manifest to app A0BCC7TTU66 and reinstall the app. Until then reactions.add returns missing_scope, which the listener swallows (the reaction silently no-ops) — answer handling is unaffected. AUTHZ-01 and the first-answer-wins CAS remain unchanged.
2026-06-23 15:11:30 -04:00
"commands",
"reactions:write"
fix(agent-team): repair Slack listener block_actions matcher; add dedicated Slack app (#25) The Socket Mode inbound listener crashed at registration time on first live run: `@app.action({})` raised `BoltError: action ({}) must be any of str, Pattern, and dict` under slack_bolt 1.28.0, killing the listener thread (the whole inbound answer path — message/app_mention/block_actions — went down, caught only by the coordinator's respawn watchdog). serve() is marked `# pragma: no cover - live socket`, so this was never exercised until the R720 bring-up. Replace the unsupported empty-dict matcher with a catch-all `re.compile(r".*")` action_id regex; handle_event still does the real filtering + AUTHZ-01 owner-allowlist gate, so over-matching is safe. Verified on sh-secrev: listener connects (live Socket Mode WebSocket), outbound chat.postMessage works, 0 errors. /sh-security-review PASS (no confirmed critical/high; matcher change introduces no new findings). Also adds the dedicated Slack app (manifest + README) backing the clarifier gate — "Sea Haven agent-team" (A0BC7AT8NUD), workspace-scoped install to avoid the Enterprise-Grid `scope_not_allowed_on_enterprise` org-install trap — and patches the provisioning runbook's stale langgraph pin (1.1.10 -> 1.2.5).
2026-06-22 13:16:35 -04:00
]
}
},
"settings": {
"event_subscriptions": {
"bot_events": [
"message.channels",
"message.groups",
"message.im",
"app_mention"
]
},
"interactivity": {
"is_enabled": true
},
"socket_mode_enabled": true,
"org_deploy_enabled": false,
"token_rotation_enabled": false
}
}
Reference in a new issue Copy permalink