write-protocol lifetime ownership and recovery barriers - #378

Open

ragnorc wants to merge 28 commits into

mainfrom

claude/interrupted-mutations-graph-drift-njvits

Commits on Jul 20, 2026

Add RFC-029: write-protocol lifetime ownership and recovery resolution barriers
claude
committed
bb55888

Commits on Jul 25, 2026

Merge remote-tracking branch 'origin/main' into claude/interrupted-mutations-graph-drift-njvits
claude
committed
053b37e
Add RFC-029 behavior probe pinning cancellation-residual lifecycle
claude
committed
0793712
Fold investigation findings into RFC-029
claude
committed
5424199
Make RFC-029 probe deterministic and record the backend-dependent residual class
claude
committed
b94c1ab
feat(server): add failpoints passthrough feature
claude
committed
ceec683
test(server): mutation dropped mid-protocol must complete without residual (RFC-029 W1, red)
claude
committed
f249815
fix(server): shield armed write protocols from caller cancellation (RFC-029 W1 Stage 1)
claude
committed
533c167
docs: write-lifetime ownership at the server boundary + stale cancellation claims
claude
committed
7d27051
feat(server): registry quarantine state and RCU publish API (RFC-029 W3 prep)
claude
committed
d7ae7b4
test(server): quarantined graphs are visible in GET /graphs and answer 503 (RFC-029 W3, red)
claude
committed
57fb5d0
feat(server): boot failures quarantine into the registry with status on GET /graphs (RFC-029 W3)
claude
committed
fe9a5eb
feat(server): supervision scaffolding — config, spawn, notify chokepoint (RFC-029 prep)
claude
committed
8537252
test(server): quarantine converges and RecoveryRequired triggers a supervised reopen (RFC-029 W3+W2(b), red)
claude
committed
36c900d
feat(server): supervised open retry loop with capped backoff (RFC-029 W3+W2(b))
claude
committed
bdf6324
docs: quarantine supervision, transient 503, RFC-029 boundary notes
claude
committed
dad1cf4

Navigation Menu

Uh oh!

write-protocol lifetime ownership and recovery barriers - #378

write-protocol lifetime ownership and recovery barriers#378
ragnorc wants to merge 28 commits into
mainfrom
claude/interrupted-mutations-graph-drift-njvits

Commits on Jul 20, 2026

Add RFC-029: write-protocol lifetime ownership and recovery resolution barriers

Commits on Jul 25, 2026

Merge remote-tracking branch 'origin/main' into claude/interrupted-mutations-graph-drift-njvits

Add RFC-029 behavior probe pinning cancellation-residual lifecycle

Fold investigation findings into RFC-029

Make RFC-029 probe deterministic and record the backend-dependent residual class

feat(server): add failpoints passthrough feature

test(server): mutation dropped mid-protocol must complete without residual (RFC-029 W1, red)

fix(server): shield armed write protocols from caller cancellation (RFC-029 W1 Stage 1)

docs: write-lifetime ownership at the server boundary + stale cancellation claims

feat(server): registry quarantine state and RCU publish API (RFC-029 W3 prep)

test(server): quarantined graphs are visible in GET /graphs and answer 503 (RFC-029 W3, red)

feat(server): boot failures quarantine into the registry with status on GET /graphs (RFC-029 W3)

feat(server): supervision scaffolding — config, spawn, notify chokepoint (RFC-029 prep)

test(server): quarantine converges and RecoveryRequired triggers a supervised reopen (RFC-029 W3+W2(b), red)

feat(server): supervised open retry loop with capped backoff (RFC-029 W3+W2(b))

docs: quarantine supervision, transient 503, RFC-029 boundary notes

Commits on Jul 26, 2026

Renumber RFC-029 to RFC-030 (0029 already assigned)

test(server): disconnect must not split the merge composite or drop the reopen signal (RFC-030 review, red)

fix(server): shield the request's effect envelope, not the engine call (RFC-030 review)

test(server): all-quarantined lenient boot must serve and converge (RFC-030 review, red)

feat(server): lenient boot with every graph quarantined serves for supervision (RFC-030 W3)

fix(server): test-only insert rejects quarantined keys (RFC-030 review)

docs: effect-envelope shielding contract, quarantine classes, RFC-030 alignment

fix(server): delete-phase RecoveryRequired reaches the trigger-B chokepoint (RFC-030 review)

test(server): boot must reject URI collisions involving quarantined graphs (red)

fix(server): from_boot rejects URI collisions involving quarantined graphs (RFC-030 review)

docs(server): record why trigger-B keeps a pending graph's backoff schedule

Merge origin/main (0.9.0 release, Lance 9.0.0 stable, private B2 core) into RFC-030 branch