Skip to content

v0.5.0 — Hardening: atomic lock, scope-gated merges, P9 digest

Choose a tag to compare

@shanemhamilton shanemhamilton released this 29 Jun 17:43
· 10 commits to main since this release
04b1607

Hardening pass driven by an overnight fleet audit (lock collisions, schedule drift, near-zero merges to main, scattered approvals).

Changed (managed protocol v3 → v4)

  • Atomic lock acquisition. Start-of-run lock goes from check-then-replace (which let two same-minute runs each declare the other "stale" and run in parallel) to acquire-or-defer: fail-if-exists create (mkdir/O_EXCL/noclobber), run token + PID + lease_until, defer when held, reclaim only a provably-dead+expired lock with a read-back ownership check.
  • Scope-gated safe-merge lane. Auto-merge only within the producer's write_scope with green gates and no production/secret/migration/deploy/CI/auth/billing/external surface. Agent tool metadata (.serena/, .beads/issues.jsonl) no longer counts as a dirty-worktree blocker; screenshot proof only for user-visible UI changes.
  • Schedule de-clustering (generator). Deterministic per-job minute staggering so same-repo jobs never share a trigger minute; phase hours preserved.

Added

  • P9 — cross-project approval digest (fleet-global). scripts/approval_digest.py reads every automation's human-approval.md (read-only), dedupes, ranks by age, filters self-resolved notes, and buckets items into "safe to batch-approve" vs "needs judgment", writing one ~/.codex/DAILY-APPROVALS.md. Optional local macOS notification; external email/Slack off unless configured + opted in.
  • Structured approval-queue items (risk/suggested_default/action/first_seen/evidence).

Verification

Self-test 24/24; live fleet 18 jobs upgraded v2→v4 with --strict PASS 19/19; atomic-lock race test (1 acquirer/round); digest dry-run across 4 projects.