[Taskmaster-1]

Phase 3 of making SynapseAI stronger: decisions reach you wherever you are, and teams get shared rules and admin sign-off. I laid a shared foundation first, three parallel agents built the features on it, and I integrated and verified them here.

Foundation

• One decision path for every channel. decisions.ts handles web, push and Slack the same way:
  • edits are re-checked against your rules;
  • undo windows apply;
  • the run is woken or parked;
  • where the decision was made is recorded (tool_calls.decided_via).
• A notifier. notify/ announces each new approval exactly once (a compare-and-set on tool_calls.notified_at) to its recipients, and reports decisions back to every channel.

Approve from your phone

• Installable app: a manifest, icons and a service worker.
• Web Push (VAPID): push notifications with Approve and Deny buttons.
  • Lock-screen approvals still go through the undo window. If your undo window is off, sends and deletes only offer Deny.
  • Device endpoints are limited to known push services, and devices that have gone away are removed.
• Email alerts (SMTP, opt-in): they link to the task only. There are no one-click approve links, because mail scanners click links.
• Settings → Notifications: devices, test push, the email toggle, and clear explanations for iPhone, unsupported browsers and an unconfigured server.

Approve from Slack

• Connection: per-user OAuth; the bot token is sealed at rest.
• The message: a Block Kit DM with the action, why it's asking, a warning when the task read outside content, and Approve / Deny / Open in Synapse.
• Button presses: the signature is checked before anything is parsed (HMAC, 5-minute window, constant-time compare). Only the person the message was sent to can act. The message updates wherever the decision is made.

Team workspaces

• Strictest answer wins: team rules and personal rules both apply, and block > ask an admin > ask > allow. A team block can't be overridden; plan grants can't skip a team block or an admin requirement.
• "Needs an admin": these calls go to the team's owners and admins (inbox, push and Slack). The member sees "Waiting for an admin".
• Joining: invite links, single use, with an expiry.
• Roles: owner, admin and member. A team always keeps at least one owner.
• Audit export: CSV per RFC 4180, guarded against formula injection.

Fixed while integrating

• Leaving the team was a loophole. A member could leave to approve their own admin-only request. Leaving or being removed now withdraws those requests and re-queues the run so the agent can respond.
• Admins and Slack: a team admin can approve a member's request from Slack. There's a test for it (decided_by is the admin, decided_via is slack).
• Signed Slack requests survive the web proxy. Checked live: a forged request gets 401 and a genuine one 200.
• Inbox header: it no longer counts "waiting for an admin" items as signed.

Schema

One new migration, 0006_reach_and_teams, plus 0005 for the foundation columns.

Testing

• 179 tests pass, plus lint, typecheck and the web build. New tests cover:
  • the notifier and decision service;
  • push: fake sender, payloads, removing dead devices, via: push;
  • email: fake transport, no approve links;
  • Slack: fake API, OAuth, signatures, clicks, message updates, admin clicks;
  • teams: composition, invites, roles, admin flow, leaving, audit CSV.
• Clicked through in the browser as an admin and a member, with fake Gmail and fake Slack: admin inbox, member waiting state, Team settings, read-only team rules, Notifications settings, Slack card. No console errors.

Not verified against the real thing

• Real Slack workspace delivery.
• Real push to a device.
• Real SMTP.

All three are covered by fakes, and each needs credentials to try (see docs/slack.md and docs/notifications.md).

🤖 Generated with Claude Code