aaltshuler 211b37e6de test(cluster): failpoint tests for crash-mid-apply and state CAS race ... The apply-side coverage the implementation spec's hard gate requires before Phase 4 graph-moving apply: - crash after the payload phase: state.json byte-identical, blobs inert on disk, lock released, no phantom statuses, nothing acknowledged; a plain re-run repairs via skip-if-exists blob reuse. - CAS race: a cfg_callback rewrites state.json at the exact read->write window (the state.lock:false concurrent-writer scenario); apply surfaces state_cas_mismatch, acknowledges nothing, reports the persisted status snapshot, leaves the concurrent writer's state on disk; a re-run converges. CI's failpoints step now runs both the engine and cluster suites. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-06-10 02:14:06 +03:00
..
ci.yml	test(cluster): failpoint tests for crash-mid-apply and state CAS race	2026-06-10 02:14:06 +03:00
codeowners.yml	ci(codeowners): un-trap required checks, auto-render, generate owner tables (#142)	2026-06-06 18:09:47 +03:00
package.yml	package caller: pass AWS secrets via secrets: inherit	2026-04-18 21:54:08 +03:00
publish-crates.yml	ci(publish-crates): set User-Agent + treat "already exists" as success (#117)	2026-05-23 14:19:17 +01:00
release-edge.yml	Add Windows release binaries (#127)	2026-05-30 14:23:40 +02:00
release.yml	fix(release): make Homebrew audit non-blocking + set up brew on runner (#140)	2026-06-06 00:44:48 +03:00