LeVCS/crates
Levi Neuwirth 255cf60a1f Check replayability on every admission, not only when a backlog exists
Two findings against the previous commit.

The replayability check sat behind an early return for "no delta layers", so
the admission right after a seal skipped it entirely — and that is exactly the
admission where everything a reopen must rebuild has just moved into the run.
Seal three entries at a ceiling of three and the next submission was accepted;
the reopen then failed with `LimitExceeded`. Only the seal attempt depends on
there being a backlog now; the ceilings are checked every time.

The open-group test did not exercise an open group. `submit` is an `async fn`,
so its send happens on first poll, and awaiting one submission before starting
the next is two groups rather than one — the refusal followed from the
published root alone, and the test passed with the pending-group projection
removed. Both submissions are now in flight: the first is polled once so it
reaches `pending`, and the second is decided while it is still there. Verified
by mutation — zeroing only the `open_group` term now fails that test and
nothing else.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XKzM69CHmBuDcA3qN1jFdh
2026-07-30 14:42:39 -04:00
..
levcs-cli Robustness fixes 2026-05-03 20:56:46 -04:00
levcs-client integrate CI and docs 2026-05-01 11:29:18 -04:00
levcs-core integrate CI and docs 2026-05-01 11:29:18 -04:00
levcs-identity Freeze Wave A: Phase 1 storage spine 2026-07-26 19:47:03 -04:00
levcs-instance Robustness fixes 2026-05-03 20:56:46 -04:00
levcs-merge integrate CI and docs 2026-05-01 11:29:18 -04:00
levcs-protocol Condition benchmark claims on the run that produced them 2026-07-29 17:38:03 -04:00
levcs-store Check replayability on every admission, not only when a backlog exists 2026-07-30 14:42:39 -04:00
levcs-tui integrate CI and docs 2026-05-01 11:29:18 -04:00