EPIC: Agent Attention Layer (superterm-inspired)

Why

A deep-dive comparison of superterm.dev vs daax (daax-dev/dx → docs/superterm-vs-daax.md, PR #91) found that superterm and daax solve orthogonal problems — superterm monitors agents, daax runs them — and that daax-web's biggest catch-up opportunity is attention UX, not architecture.

Crucially, daax already collects the data superterm has to screen-scrape: watchtower ingests structured Claude Code hook events, including the Notification (permission/idle-prompt) event. So daax-web can deliver a more precise attention layer than superterm with mostly frontend work.

Goal

Make daax-web the best place to stay on top of many agents at once: see every session's status at a glance, get alerted the instant one needs you, redact secrets for screen-share, and unblock from your phone.

Workstreams & sequencing

1. #153 — Attention board (flagship; foundation for everything below)
2. #154 — Blocked-agent detection + notification bell (depends on #153; backend signal already exists in watchtower)
3. #155 — Presentation / mask mode (independent; cheap; can run in parallel)
4. #156 — Mobile unblock PWA (depends on #153 + #154)

#153 ──┬──> #154 ──> #156
       └──────────────^
#155  (parallel, independent)

Out of scope (deliberate divergence from superterm)

• tmux-native "bring your own session" — conflicts with daax's launch-owned model.
• Re-building terminal/recordings — already complete in daax-web.

Definition of done

• #153 #154 #155 #156 closed
• A developer running 3+ agents can: glance at one board, be alerted when any blocks, screen-share safely, and unblock from a phone.

Created as DRAFT pending JP approval; flip the sub-issues to APPROVED to start work.

Start with docs/superterm-vs-daax.md and review the linked workstreams #153, #154, #155, and #156 in their stated sequence. The epic is done when those sub-issues are closed and developers can monitor multiple agents, receive blocking alerts, screen-share safely, and unblock an agent from a phone.