omnigraph/crates
Claude a9c4423b82 Strengthen cleanup-then-optimize sequencing test with postconditions
Reviewer feedback on PR #62: the original
`cleanup_then_optimize_succeed_in_sequence` only unwrapped both calls
and asserted nothing, so it didn't validate the claimed sequencing
behavior. The concern that motivates the test is that cleanup destroys
version history and optimize on a freshly-cleaned table could trip on
dropped fragment refs or stale manifests.

Rename to `cleanup_then_optimize_preserves_rows_and_table_remains_writable`
and add three concrete postconditions: row counts in both Person and
Company tables survive the sequence; the head remains readable; and a
subsequent merge load still succeeds.
2026-05-12 23:36:01 +03:00
..
omnigraph Strengthen cleanup-then-optimize sequencing test with postconditions 2026-05-12 23:36:01 +03:00
omnigraph-cli release: prepare omnigraph 0.4.2 2026-05-10 14:02:28 +00:00
omnigraph-compiler release: prepare omnigraph 0.4.2 2026-05-10 14:02:28 +00:00
omnigraph-server Drop redundant server-level regression test 2026-05-11 21:57:47 +00:00