rvwlisted

# rvw review comments Use only the `rvw` CLI protocol to access rvw state. Never read or edit the SQLite database directly. Require a local Agent with access to the saved repository. A running rvw viewer can provide database access through its user-only Unix socket; require direct rvw data-directory access only when that route is unavailable. Do not guess comment contents when required access is unavailable. ## Preflight 1. Run `rvw protocol --json` and parse stdout as JSON. 2. Require `protocolVersion` 4, `agent.transport`, and every task capability needed for the task. Require `comment.codeReferences` whenever reading or writing typed post references. 3. Run `rvw agent status --json`. Read `socketPath`, `connectionResult`, `selectedDatabasePath`, `selectedTransport`, and `fallbackReason`. If `selectedTransport` is `unavailable`, stop and report the diagnostic; an explicitly configured `RVW_AGENT_SOCKET_PATH` never falls back to direct database access. Otherwise use the reported transport without overriding it. 4. Prefer the CLI's transparent Unix-socket route when a normally launched rvw viewer is running. Explain the exact local permission needed only if both the socket route and direct CLI access are unavailable. `RVW_DATABASE_PATH` selects an explicitly managed database path; the CLI uses a running viewer only when it reports that same database. ## Create comments Create a new root thread only when the user explicitly asks to record review findings in rv