/feedback does not surface drafts queued by the SendFeedback tool

Description

The SendFeedback tool (available to Claude when it uses it on the user's behalf) writes draft feedback reports to ~/.claude/feedback/drafts/*.json with status: "queued". The tool's own description states:

"The draft is QUEUED LOCALLY. It is never sent without the user's explicit approval... The user can review and send it with /feedback."

However, running /feedback in the CLI only opens a box to compose a brand-new report from scratch. It does not show, list, or offer to send any of the drafts already sitting in ~/.claude/feedback/drafts/.

Steps to reproduce

1. Have Claude (in a Claude Code session) call the SendFeedback tool at least once — this writes a JSON file to ~/.claude/feedback/drafts/.
2. Run /feedback in the CLI.
3. Observe that the modal/box that opens is for writing a new report, with no visible way to review or send the file(s) already queued.

Expected behavior

/feedback should let the user review the queued drafts (title, details, etc.) and choose which to send, matching what the tool's own description promises.

Actual behavior

/feedback appears disconnected from ~/.claude/feedback/drafts/ — queued drafts have no discoverable send path from the CLI.

Environment

• CLI version: 2.1.277
• OS: macOS (darwin arm64)
• Install: (not captured — general npm/native install)

Additional context

Confirmed on disk: draft JSON files exist with status: "queued", each containing draft_id, type, title, details, area, task_category, trigger, effort, and a transcript_ref pointing at the originating session's .jsonl file. There is no companion mechanism (CLI flag, keyboard shortcut, separate command) found in code.claude.com/docs that exposes this queue.