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
..
src	fix(cluster,cli): apply failure output — persisted statuses only, changes list printed	2026-06-10 00:35:03 +03:00
tests	test(cli): cluster lifecycle e2e — real-graph import/apply/refresh, schema-change loop, force-unlock retry	2026-06-09 23:44:49 +03:00
Cargo.toml	Merge origin/main into cluster-config-docs	2026-06-09 18:11:12 +03:00