omnigraph/crates
aaltshuler 5e1dede08f fix(cluster,cli): apply failure output — persisted statuses only, changes list printed
Two review findings (greptile, PR #165):

- ApplyOutput.resource_statuses on a failed state write now carries the
  pre-apply on-disk snapshot instead of the in-memory mutations that were
  never persisted, so automation reading the field independently of `ok`
  cannot see phantom applied/blocked statuses. Regression test forces the
  state write to fail via a read-only __cluster dir (unix-only, skips when
  permissions are not enforced).
- Human-mode `cluster apply` prints the classified changes list on failure
  too, so an operator debugging a partial apply without --json sees what was
  attempted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-10 00:35:03 +03:00
..
omnigraph fix(unique): collision-free tuple key shared by intake and merge, loud on un-keyable types (#160) 2026-06-09 19:28:21 +02:00
omnigraph-cli fix(cluster,cli): apply failure output — persisted statuses only, changes list printed 2026-06-10 00:35:03 +03:00
omnigraph-cluster fix(cluster,cli): apply failure output — persisted statuses only, changes list printed 2026-06-10 00:35:03 +03:00
omnigraph-compiler release: v0.6.2 2026-06-09 15:59:59 +02:00
omnigraph-policy release: v0.6.2 2026-06-09 15:59:59 +02:00
omnigraph-server release: v0.6.2 2026-06-09 15:59:59 +02:00