Query receipt summaries from the persisted chain (most recent first). Never returns full file contents.

Verify the integrity of the receipt chain using the stored public key. Returns ok, brokenAt, reason, and entryCount.

Report Lotor runtime status: home path, receipt count, chain integrity, current herding mode (herded | grazing | loose | custom), whether the human-signature gate is set up, and whether the hooks that actually record and gate are registered in Claude Code settings. Call this at the start of a session or whenever the user asks about Lotor. If gateInitialized is false, walk the user through running npm run setup in a terminal to set their signing passphrase (this needs a real terminal; you cannot do it for them). If hooksRegistered.preToolUse is false, nothing is gated regardless of gateInitialized: point the user at the README install steps. Always tell the user the home path so they can see where the runtime lives.

Execute a gated action with approval token. FAILS CLOSED: without a valid approval token, returns decision:denied.