v0.6.0 — the Cursor adapter

rungraph now reads Cursor — the fifth adapter, and the fifth client that can run the MCP loop.

Cursor is two stores under one adapter, because the rail should show one vendor for one product: the IDE's global state.vscdb (every project's conversations in one key-value table) and cursor-agent's per-chat store.db (a content-addressed blob store whose conversation order lives in a protobuf root snapshot). Runs carry surface: 'ide' | 'cli'.

No Cursor field says whether a tool call succeeded — a refused command is status: completed — so a calibrated outcome classifier shared by both surfaces decides, and the calibration record ships in the spec. Cursor's own encryption-key fields never leave the machine: the secret scanner learned a key-name rule alongside its pattern list.

Also in this release: dogfood and readability fixes across the dashboard, and the Claude Code adapter recognises atis-latch with a populated token and bridge sessions, and names MCP tools.

Like Hermes and opencode, the Cursor stores are SQLite: those three adapters want Node ≥ 22.13 and self-disable with a structured warning on older Nodes.