v0.2.0 — Execution Safety

Highlights

• Fenced leases with opaque lease tokens and monotonic generations prevent stale executors from reporting progress or completing a reclaimed task.
• Execution-attempt audit history, delayed retry backoff, cooperative cancellation, and idempotency conflict detection improve recovery after network or lease failures.
• Completion is replay-safe when the task state commits but the client loses the response.
• The bridge remains read-only: unregistered task types and write-capable operations are rejected.
• Added global Codex MCP setup documentation for reuse across new desktop, CLI, and IDE conversations on one host.

Upgrade note

Grok executors must pass the lease_token returned by claim_next_task to lease renewal, progress, result-attachment, completion, and failure calls. Update any Routine instruction before using v0.2.0.

Verification

npm run check, npm test, npm run build, local end-to-end smoke testing, and staging protocol checks passed.