fix(tui,dashboard): force clean repaint on focus regain, session resume, and PTY reattach

[teknium1]

Summary

Completes the stale/duplicated-chrome sweep on the two remaining surfaces after #86260 (classic CLI): the Ink TUI and the dashboard's embedded terminal now force a clean repaint at the three moments they previously trusted stale incremental state — terminal focus regain, session resume, and keep-alive PTY reattach.

Root cause across all three: differential renderers (Ink cell-diff, xterm ANSI-tail replay) repaint against a previous frame that no longer matches the physical surface, so the transcript shows ghosts, stale rows, or comes back blank.

Changes (salvages 3 contributor PRs, authorship preserved)

• fix(tui): redraw after terminal focus regain #25337 (@John-Lussier) — TUI: forward DECSET 1004 focus transitions from the Ink App wrapper to the renderer; on focus-in, reassert terminal modes and force one full redraw instead of trusting pre-blur incremental frame state (TUI twin of the classic-CLI focus fix in fix(cli): resolve the duplicated prompt/status chrome class (interrupt, resize, focus regain, tmux attach) #86260)
• fix(ui-tui): redraw after session resume #62187 (@LeonSGP43) — TUI: force a full Ink redraw (evictInkCaches + forceRedraw) on the immediate resume snap after switching sessions, fixing the stale first paint ([Bug]: TUI shows stale session content after switching sessions (v0.18.1) #62170); resume-scroll helper extracted to sessionResumeView.ts with focused coverage. Conflict resolved to keep main's newer signalFreshSessionBoundary alongside the moved helper
• fix(dashboard): redraw TUI after PTY reattach #68071 (@algf) — dashboard: /api/pty requests a complete TUI redraw (Ctrl-L to the bridge) when reusing a keep-alive PTY; a bounded raw ANSI tail is not a self-contained frame, so reconnects to long sessions restored only the recent status/prompt rows and left the transcript blank. First-attach behavior unchanged

Validation

Suite	Result
pytest: test_pty_session, test_pty_keepalive_ws, test_web_server_pty_reconnect	15 passed
vitest: App.focus.test, sessionResumeView.test, useSessionLifecycle.test	12 passed
tsc --noEmit (ui-tui)	clean
attribution audit	all mapped

Base current with origin/main at push time; each contributor commit cherry-picked individually (rebase-merge ready).

Infographic

[coderabbitai]

Warning

Review limit reached

@teknium1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2362a454-128f-47c7-aa23-53af599adee4

📥 Commits

Reviewing files that changed from the base of the PR and between d29abb7 and dd44187.

📒 Files selected for processing (11)

• contributors/emails/andrew.lg.ford@gmail.com
• hermes_cli/pty_session.py
• hermes_cli/web_server.py
• tests/test_pty_keepalive_ws.py
• tests/test_pty_session.py
• ui-tui/packages/hermes-ink/src/ink/components/App.focus.test.tsx
• ui-tui/packages/hermes-ink/src/ink/components/App.tsx
• ui-tui/packages/hermes-ink/src/ink/ink.tsx
• ui-tui/src/app/sessionResumeView.test.ts
• ui-tui/src/app/sessionResumeView.ts
• ui-tui/src/app/useSessionLifecycle.ts

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

૮ >ﻌ< ა ci review

_{ran on dd44187 — chore: contributor email mappings for salvaged PRs}

⚠️ Warnings

OSV vulnerability scan · View job

5 known vulnerabilities found in pinned dependencies.

• CVE-2026-67213 in package-lock.json
• CVE-2026-67213 in website/package-lock.json
• CVE-2026-70608 in package-lock.json
• CVE-2026-56876 in package-lock.json
• CVE-2026-70606 in package-lock.json

How to fix:

Review the findings in the Security tab. Update the affected dependencies if a patched version is available.

---

debug info

CI timings

CI timings · View report · View job

Wall time 8m17s vs 11m22s (-27.1%). 15 job(s) slower, 21 faster, 1 unchanged.

• Check contributors / check-attribution: -170.0s
• Detect affected areas: -140.0s
• OSV scan / Emit review status: -99.0s
• Python tests / Generate slices: -95.0s
• Python tests / Run tests slice 11/12: -78.0s