feat(channel): support lifecycle channel startup control

[PsiACE]

Summary

Channels are enabled by the following rules:

• Interfaces are enabled only if explicitly included.
• Lifecycles are always enabled unless explicitly excluded.
• Regular channels depend on the values of include and exclude.
• support !channel exclusions in enabled_channels / --enable-channel

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	bub	457e6cf	Commit Preview URL Branch Preview URL	May 25 2026, 09:46 AM

[PsiACE]

Previously, bub-mcp only registered remote tools after its lifecycle channel was started, which meant commands like bub chat did not naturally expose MCP tools. This change allows to mark bub-mcp an auto-start lifecycle channel so MCP tools are mounted by default in channel runtimes, while adding exclusions such as !mcp.lifecycle for debugging or for intentionally disabling MCP services.

[frostming]

The property names start_with_channels and role are a bit cryptic, making it hard to understand what they are supposed to do. Alternatively, using channels to manage lifetime is purely a matter of convenience; it's not obvious from the class name that they are meant to handle this.

My suggestion is to subclass Channel as Lifecycle and Interface(names can be discussed), and make those properties hidden from users.