[BUG] Plan-file inline comments ("Leave a comment for Claude") don't reach the model on resume

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Summary
The plan-review UI shows "Leave a comment for Claude…" on hover for each line of the plan file. Comments left this way are visible in the client's right pane but are never delivered to the model — not in the approved-plan payload, not in the plan file on disk, and not through any other channel the model can access.

What does work
Direct file edits made by the user in the plan review UI do come through (they modify the file on disk). So the model can see changes the user types directly into the plan text.
Comments do not. They live only in the client UI.
Tested twice in one session
First test (organic): User left 4 substantive comments on a dashboard plan (field corrections, scope changes). Model couldn't see any of them. User had to screenshot each comment one-by-one and paste into chat.
Second test (controlled): Model wrote 3 marked lines ("Comment test line A/B/C") explicitly asking the user to leave comments. User confirmed comments were visible in the right pane. After approval, all 3 lines came back clean — no comments attached.
Impact
Plan comments are the only structured way for a user to give line-level feedback on a plan without rewriting the plan text. When they don't work:

The model builds the wrong thing (missing field corrections, scope changes, business logic overrides)
The user has to re-communicate feedback through screenshots or chat — defeating the purpose of the feature
Trust in the planning workflow erodes ("why does it say 'for Claude' if Claude can't read it?")
Suggested fix
Either:

(a) Merge comments into the plan file on approval as inline annotations (e.g. <!-- user: comment text --> next to the target line)
(b) Append a ## User Comments section to the approved-plan payload in the ExitPlanMode tool result, with line references
(c) Deliver them as a follow-up user message after plan approval
Option (a) is the most durable — it survives the model re-reading the file later.

Environment
Claude Code (desktop app, macOS)
Model: Claude Opus 4.6 (1M context)
Date: 2026-04-15

What Should Happen?

The model can read the comments after approval — either embedded in the plan file, appended to the ExitPlanMode tool result, or delivered as a user message.

Actual: The model receives the plan with zero trace of the comments. The plan file on disk is byte-identical to what the model wrote pre-approval. The approved-plan payload in the ExitPlanMode result also omits them. The model has no tool or API to access the client's annotation layer.

Error Messages/Logs

Steps to Reproduce

Enter plan mode — model writes a plan to the plan file
Model calls ExitPlanMode
In the plan review UI, hover on any line and click "Leave a comment for Claude…"
Type a comment and click "Comment"
Confirm the comment appears in the right-side annotation pane
Click Approve
Expected: The model can read the comments after approval — either embedded in the plan file, appended to the ExitPlanMode tool result, or delivered as a user message.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.2773.0 (884b37) 2026-04-15T14:32:09.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_