- Slack + outbound push when an output is promoted to memoryRev 26 made promote-to-memory a one-click operator move — the explicit signal that 'this insight should outlive the artifact's lifecycle.' Until rev 32 the action was silent: only operators staring at the dashboard knew the team's collective memory had grown. Now every promotion fires a Slack ping (with the kind, importance, and content excerpt) and dispatches a new memory.promoted outbound webhook event so downstream automations (a CRM, a wiki, a knowledge base) can mirror durable knowledge as it accumulates.
- Pinned outputs (close 4-entity pinning symmetry)Memory pinning shipped rev 5; signals rev 22; tasks rev 23. Rev 32 closes the symmetry on the fourth core entity. A pinned output stays at the top of the approval queue regardless of how many fresh outputs land below it — the load-bearing brief, decision, or draft you want the team to actually see, not buried under noise. Pin button mounts inline next to the existing share/regenerate/promote chips. New PATCH /api/artifacts/:id/pin endpoint and the pinned visual treatment matches the rev-22/23 pinned panels for design consistency.
- Cost spike detectionCompanion to the rev-21 cost cap warning. Where the cap warning fires only when an explicit dollar ceiling is configured, the spike detector fires whenever today's spend is at least 2× the trailing 7-day daily average and at least $0.50 absolute — even on workspaces with no cap. Catches a runaway noisy source or stuck loop before it eats the day's budget. Surfaces as a dismissible amber banner at the top of the dashboard (6h localStorage suppression so a real spike re-surfaces the next day) and pushes a Slack alert + workspace.cost_spike outbound event from the daily cron, rate-limited to once per workspace per day. New OutboundEvent: workspace.cost_spike.
- Inline reply from the mentions inboxRev 30 added the mentions inbox; rev 31 added permalinks so a click from email or Slack lands on the exact comment. Rev 32 closes the open-and-respond loop. Tap Reply on any unread mention in the inbox and an inline textarea appears — Esc to cancel, post to send. The reply lands as a threaded comment under the original mention (parentCommentId set) so it folds under the thread automatically. Three-second action vs the previous scroll-into-thread → type → scroll-back loop.