feat(cli): agent bridge

docs/agent-guide/logseq-cli/001-logseq-cli.md

@@ -112,6 +112,8 @@ The top-level help groups commands into graph inspection/editing, graph manageme
 
 - `login`
 - `logout`
+- `agent bridge`
+- `agent bridge list`
 - `completion`
 - `debug pull`
 - `skill show`
@@ -120,6 +122,12 @@ The top-level help groups commands into graph inspection/editing, graph manageme
 
 `example` entries are generated from command metadata for the inspect/edit families `list`, `upsert`, `remove`, `query`, `search`, and `show`. Use exact selectors such as `example upsert page` or prefix selectors such as `example upsert`.
 
+### Agent bridge
+
+`agent bridge` is the first AgentBridge command surface. It resolves the target graph using normal CLI config precedence, resolves the AgentBridge name from `:agent-name` in `cli.edn` or the machine hostname, checks that `codex` is available, starts or reuses the graph's db-worker-node, registers the AgentBridge name in the graph, scans TODO `#Task` blocks assigned to that AgentBridge name, and listens to db-worker-node events for follow-up scans. Matched tasks are routed to `codex exec --json`; the bridge records the Codex session/thread id in `agent-bridge-sessions.edn` and writes it to the task's `agent-session-id` property. `--dry-run` performs the setup and scan but only prints the Codex commands it would run.
+
+`agent bridge list` reads root-dir scoped bridge session records from `agent-bridge-sessions.edn`. Human output uses the columns `SESSION`, `STATUS`, `BACKEND`, `GRAPH`, `BLOCK`, `AGENT`, `STARTED`, and `UPDATED`, ending with `Count: N`. Completed sessions are hidden by default; use `--all` to include them.
+
 ## Global flags and output modes
 
 Global flags are defined in `logseq.cli.command.core/global-spec`: