vbot-clilisted

# vBot CLI Use `vbot` through the shell Tool to inspect and configure the application. The server runs Agents and owns the state used by the CLI, WebUI, Desktop, and Channels. A saved configuration change affects that server instance. Choose the area and action first: `vbot <area> <action> [target] [options]`. Related actions can be grouped, for example `vbot project override set`, `vbot channel token set`, and `vbot skill file write`. There is no fixed word count. Resource ids are positional; flags supply options and values. Use the commands shown by help instead of inventing action flags such as `--restart`. Start with `vbot help` or `vbot <area>`, then narrow to `vbot <area> <group> --help`. Bare command groups show help without executing an action. Collection plurals also work; prefer the names and action paths shown in help. Older compound command spellings remain compatible. Syntax errors may suggest a correction but never execute it automatically. `[OK]` confirms command completion; `[WARN]` calls out pending work or a reported limitation; `[ERROR]` marks failure. Read the returned state before claiming runtime readiness. Progress and completion notices for management commands go to stderr; stdout retains the data, including complete JSON and content reads. `--output plain` suppresses these extra notices and uses the stable data layout. Terminal output is readable by default; `--output human` requests that layout in a capture too. Lifecycle and Doctor commands reta