[P7] Inspect reviews and manage attention in the TUI

[richhaase]

---

steward_contract: "3"
id: "tui-review-attention"
title: "Inspect reviews and manage attention in the TUI"
revision: 1
state: draft
created_at: "2026-07-30T16:34:04Z"
approved_at: null
approved_by: null
frozen_body_sha256: null
supersedes: null

Inspect reviews and manage attention in the TUI

Outcome

Users can understand a pull request's review state and clear or defer actionable work without losing its history.

Scope

GitHub review mutations are delivered separately.

Acceptance

• AC1: Pull request detail shows the current review result, relevant history, dispositions, uncertainty, and why automation is waiting or stopped.
• AC2: Raw or non-actionable findings remain inspectable with the decision that removed them from the actionable queue.
• AC3: Defer, snooze, release, resume, retry, cancel, and resolve actions affect attention without erasing history.
• AC4: Background updates cannot silently change the pull request or head targeted by an attention action.
• AC5: Existing acr and acr watch workflows remain available without an auxiliary TUI command family.

[richhaase]

Downstream impact from #191 / PR #221 dogfood — July 22, 2026

• Changed: The approved Epic amendment adds durable adjudication memory, review economics, convergence controls, and a PR [P1] Enforce trusted review-configuration sources #221 replay corpus.
• Contract now: The console and one-shot surface must expose budgets, usage, prior dispositions, suppressed output, and why automation continued or stopped.
• Compatibility or migration impact: Additive planning contract; no current CLI behavior changes.
• Required follow-up: The issue acceptance criteria are amended below and implementation must coordinate with #223 and #224 where applicable.
• Evidence: Epic amendment and PR #221.

[richhaase]

Downstream impact from #243 / PR #244

• Changed: internal/desk.Refresh/LoadStored no longer keep a tracked PR in the inbox solely because a PRSnapshotV1 exists on disk.
• Contract now: a tracked key that drops out of discovery is retained only if it has real history (a review run or a lifecycle event) — a bare, history-less sighting ages out automatically instead of pinning the PR forever.
• Compatibility or migration impact: no schema/migration change; review-detail/actions operate on whatever items the desk Inbox surfaces, and a bare-sighting item may now disappear between refreshes instead of remaining actionable indefinitely.
• Required follow-up: none.
• Evidence (PR, tests, fixtures): PR fix: desk tracking requires real history to survive dropping out of discovery #244; TestRefresh_BareSnapshotWithNoHistoryDoesNotSurviveDroppedSearchResult, TestLoadStored_ExcludesBareHistorylessTrackedKey, TestRefresh_ContinuingResponsibilitySurvivesDroppedSearchResult (updated) in internal/desk/inbox_test.go.