v0.11.0 — Durable agent revocation

Highlights

• Durable agent revocation — authenticated revocation fences new requests and tool admission, cancels active request contexts, persists irreversible tombstones, and waits for admitted local dispatches to drain before acknowledging. API and UI listeners share one fence. (#54, #55)
• Content-free dispatch audit — records admitted, refused and completed dispatch IDs, including dispatch admitted before revocation. Revoked prompt snapshots are removed after the final handler exits.
• Managed retry recovery — includes the duplicate failure-replay fix from the historical v0.10.1 source tag: failed calls can recover after backend state changes, repeated same-class failures are suppressed, and ambiguous mutating failures require state verification. (#49, #50)

Deployment contract

Set CLAW_REVOCATION_DIR to persistent storage with one trusted proxy writer. Missing or corrupt initialized storage fails closed. The 16 MiB ledger capacity limit refuses new durable acknowledgements without closing unrelated identities. Revocation cannot undo remote effects already dispatched.

Verified: full unit suite, vet, proxy race tests repeated twice, and independently reproduced per-run Docker/PicoClaw supervisor spikes against the integrated source. The published image covers linux/amd64 and linux/arm64.

Image: ghcr.io/mostlydev/cllama:v0.11.0