Hunk Review

Treat Hunk as the user's interactive review UI. Never launch an interactive hunk diff or hunk show inside the agent terminal. Inspect and control an existing session through structured resources or hunk session ….

Choose the control path

1. Harness resources: When hunk:// reads are supported, prefer hunk://review?repo=…, hunk://context?repo=…, and hunk://comments?repo=…. Read hunk://review first; request raw patch content only for files that need close review.
2. Session CLI: Use hunk session list|get|review|context|navigate|reload|comment when internal resources are unavailable or mutation is required.
3. Resumable worktree UI: Use hunk resume or this repo's paired launcher to reopen the last source associated with a Git worktree.
4. Agent context file: Use --agent-context only when notes already exist as a sidecar and no live session should be steered.

Read references/live-review.md for the complete workflow and references/worktree-resume.md for paired worktree behavior.

Start with structure