Module commands 

The transport-neutral :ai-log ex-command.

:ai-log is always registered (register_ai_log_command, no #[cfg]): the log substrate lives in the lattice-agent port (AG‑3), so the command is meaningful for whichever transport(s) are compiled in. It captures no handle: opening the per-process *ai:<provider>:<index>* buffer needs host buffer-open machinery, so it emits Effect::OpenAiLog and the host resolves it (0 known sessions echo a hint, 1 opens directly, >1 raises a picker) – exactly how :lsp-server-log is wired.

The ACP lifecycle commands (:opencode / :ai-prompt / :ai-stop) live in crate::acp::commands, gated with the rest of the ACP transport.

Functions

register_ai_log_command

Register the transport-neutral :ai-log [provider] command. Captures NO handle: the host reads the AiLogger service to enumerate sessions and open the *ai:<provider>:<index>* buffer. The crate owns the BINDING + the emission here (mode-ownership); the host owns only the generic buffer open. Mirrors :lsp-server-log. Always available (both transports log through the shared port substrate).