UX: Add blocker lifecycle explanation and recovery guidance

[frankbria]

Problem

The Blockers page shows blockers without context on how they were created or what 'answering' a blocker means for task execution. Users see an answer input but don't understand the impact.

Impact

Users unsure if answering a blocker will resume execution, require a new execution start, or do nothing. This uncertainty leads to abandonment or incorrect recovery attempts.

Recommendation

1. Add info banner at top of blockers page: "Blockers pause AI execution. Answer below to provide the information needed to continue."
2. Show blocker context in detail view: which task created it, what triggered it (stall timeout, missing file, agent request)
3. After answering: show confirmation "Answer recorded. The agent will resume when you restart execution."
4. Add 'Resume Execution' shortcut button where appropriate

Acceptance Criteria

• Intro banner explains blocker purpose and lifecycle
• Blocker detail shows originating task and trigger reason
• Answer confirmation shows the exact next action required
• User understands recovery flow without external docs
• Works for both system-created and agent-created blockers

Affected Components

web-ui/src/app/blockers/page.tsx

[coderabbitai]

🔗 Related PRs

#18 - feat(049-human-in-loop): Complete human-in-the-loop blocker system (Phases 1-9) [merged]
#390 - feat: Blocker Resolution View - Answer Agent Questions [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[traycerai]

Warning

Something went wrong while processing your request.

Reference ID: 7dbd731d-d2af-4008-a0ac-c8f6c80d3bf0

Please try again or contact support if the issue persists, referencing this ID.