History resume got less haunted

Kaji now handles provider-history resumes more carefully, especially when routing from Ask into existing terminal sessions.

The resume path was moved off the blocking path, history annotations were resolved more reliably, and the default terminal resume flow was tightened so old sessions do not drag the UI into a swamp.

• Resolved history annotations before dispatch
• Launched history resumes asynchronously
• Skipped expensive session scans for history resumes
• Prevented a resume seed update loop
• Separated Codex resume prompt behavior from other providers

Browser persistence polish

Browser state now survives project switches more reliably, browser tabs compress better, and temporary Playwright MCP artifacts are ignored so the repo does not collect crumbs from browser automation.

• Preserved browser sessions across projects
• Made browser tabs responsive
• Removed temporary Ask hang diagnostics after the issue was narrowed