- retitled "group commit, and the async barrier"; the 2026-08-15/20/28
banners compressed into a trail; `readiness: refine`, `review_pending`
(forks 1–5 and 8–10 decided under autonomy 2026-09-10 by codd-shoney;
6 and 7 keep readiness at refine)
- what part B is FOR: the read tail on shard 0 while a barrier blocks — and
only that; mechanism: the drain pwrites as today, then submits ONE bare
IORING_OP_FSYNC and keeps working; held replies released by the
completion; the epoll fallback is part A unchanged; ordering with
compaction and the deferred drops/re-points; the inline durable write on
shard 0 unified through its own inbox while a barrier is in flight;
completion delivery on a busy shard 0; shutdown reaps an in-flight
barrier before wo_wal_close
- fork 6 (kernel floor and raw-syscall shape) goes to lintor; fork 7
(go/no-go) is settled by one measurement — tmpfs vs ext4 `mixread.p99` —
then one developer answer; both answers already sit in
.dev/zack/databasev2-4b.md, the fold into this story is pending
- progress table B1–B9 with sizes and owners (cyril B1/B8, lintor B2, the
runtime agent B3, codd + pm B9); no new knob, no new dependency
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
(cherry picked from commit 7ceb7b8805da41e67661744746bf2d0b7879cc50)
shoney.arickathil
15b15dbe1c