Greptile Summary

This PR breaks potential module initialization cycles on Windows bundled builds by redirecting imports of the CHANNEL_IDS and CHAT_CHANNEL_ORDER constants to the lighter-weight leaf module src/channels/ids.ts instead of routing through src/channels/registry.ts. The registry.ts module re-exports those constants from ids.ts (so existing callers remain unaffected), but eagerly requiring it also pulls in plugin runtime state machinery — which can produce undefined/null not-iterable startup errors when the module evaluation order in a bundle happens to read those arrays before they are initialized.

Key changes:

• src/channels/ids.ts is established as the single source of truth for built-in channel ID constants (CHAT_CHANNEL_ORDER, CHANNEL_IDS, ChatChannelId).
• Six files that only needed the constants — config schema, config validation, CLI channel options, elevated-allowlist matcher, plugin registry sorter, and setup-registry sorter — are updated to import directly from ids.ts.
• Runtime helpers (normalizeAnyChannelId, normalizeChatChannelId) that legitimately depend on registry state are retained on registry.ts imports unchanged.
• src/channels/registry.ts continues to re-export the constants from ids.ts, so all other call-sites continue to work without changes.

Confidence Score: 5/5

• Safe to merge — a clean, minimal import-path refactor with no behavioral changes.
• Every changed file only redirects constant imports (CHANNEL_IDS, CHAT_CHANNEL_ORDER) from registry.ts to the new leaf ids.ts. All runtime helper calls (normalizeChatChannelId, normalizeAnyChannelId) are correctly kept pointing at registry.ts. The registry.ts still re-exports those constants from ids.ts, so the wider codebase is unaffected. No logic was altered, no new state was introduced, and the fix directly addresses the described Windows bundled-build startup regression.
• No files require special attention.

_{Last reviewed commit: 2f3e7c0}