[BUG] /resume does not list recently renamed sessions despite JSONL files existing on disk

Bug Description

Sessions renamed with /rename do not appear in the /resume interactive list, even when they are among the most recently updated sessions. Attempting to resume by session ID prefix also fails with "Session not found."

Steps to Reproduce

1. Start a Claude Code session in a project directory
2. Do some work (the session accumulates messages)
3. Rename the session with /rename <descriptive name>
4. Confirm rename succeeds: Session renamed to: <name>
5. Exit the session
6. Start a new session in the same directory
7. Run /resume — the renamed session does not appear in the list
8. Run /resume <session-id-prefix> (e.g., /resume 4a2dcc92) — returns "Session not found"

Expected Behavior

• The renamed session should appear in the /resume list (sorted by recency)
• /resume <session-id-prefix> should match and resume the session

Actual Behavior

• The session is completely absent from the /resume list
• Direct ID prefix lookup also fails
• The session's JSONL file exists on disk and contains valid data including the rename record

Investigation

Verified the following on the affected session (4a2dcc92-a072-460f-9224-febaff512e4d):

• JSONL file exists: ~/.claude/projects/<project>/4a2dcc92-...jsonl (1.1 MB, 384 lines)
• Last updated: 2026-06-04T08:45:04Z (7th most recent out of 46 sessions)
• Rename recorded in JSONL: The file contains a local_command entry with /rename and a confirmation Session renamed to: ...
• File is readable: Valid JSON on every line, standard structure with sessionId, uuid, timestamp fields
• Other recent sessions (without rename) appear normally in /resume

JSONL rename entry (excerpt)

{
  "type": "system",
  "subtype": "local_command",
  "content": "<command-name>/rename</command-name>\n<command-args>管理画面: ビールメニュー詳細で「国」フィールドが表示されていない</command-args>",
  "timestamp": "2026-06-04T08:40:38.998Z",
  "sessionId": "4a2dcc92-a072-460f-9224-febaff512e4d"
}

Hypothesis

The /resume command may be using an index or cache that is not updated when a session is renamed. Or the rename metadata is stored separately from the JSONL, and the lookup mechanism fails to correlate the two.

Related Issues

• #57203 — Sessions missing from claude --resume list (similar symptom, different trigger)
• #49128 — /resume shows "No conversations found" despite sessions on disk

Environment

• Claude Code version: 2.1.98
• OS: macOS Darwin 25.3.0
• Shell: zsh
• Total sessions in project: 46
• Platform: Apple Silicon