--resume fails with --dangerously-load-development-channels: 'No conversation found'

Description

When using --dangerously-load-development-channels server:<name> together with --resume <session-id>, Claude Code always returns:

No conversation found with session ID: <uuid>

The .jsonl session file exists on disk at the expected path (~/.claude/projects/<encoded-path>/<uuid>.jsonl), and --resume works fine without the channels flag.

Steps to reproduce

1. Launch a session with channels:

``
claude --dangerously-skip-permissions --dangerously-load-development-channels server:telegram --name test
``

1. Do some work, then exit
2. Try to resume:

``
claude --dangerously-skip-permissions --dangerously-load-development-channels server:telegram --resume <session-id>
``

Expected: Session resumes with channel support active
Actual: No conversation found with session ID: <uuid>

Environment

• Claude Code v2.1.80
• macOS (Darwin 25.3.0)
• Channel server: Telegram plugin MCP server via bun (stdio transport)

Impact

This means any session using development channels loses its conversation history on every bounce/upgrade. The workaround is to launch fresh and have the session re-read its CLAUDE.md and memory, but this wastes context and loses in-conversation state.

Notes

• --resume works correctly without --channels or --dangerously-load-development-channels
• --channels plugin:telegram@claude-plugins-official + --resume was not tested (only the server: variant)
• The session file is definitely present on disk — confirmed with ls -la