Recover durable context mounts on current main #270
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/prolog-rlm!270
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rage/223-durable-context-mount-recovery"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Recovers Slice 2 of #223 from stale/conflicted #228 without rewriting shared history.
RAGE baseline
Starts from exact canonical
main7f0050f524db6de5293163241176ac4660f04349after Slice 1 landed. The old #228 branch is 42 commits behind current main and contains obsolete Slice-1 benchmark history, so this recovery preserves only the generic durable-context-mount slice rather than force-rewriting that shared branch.TDD recovery
All approved durable-mount defect contracts are now pinned and repaired on current main:
latest -> reusable? -> puttransaction by store + mount key;Realization
persistent_mount_cache/4includes artifact-store identity;rlm_artifactsemantics;Validation
Exact head
680fdcc368343a8e2bfbd183496130e7186780a9:Non-goals
No provider/planner changes, no second persistence plane, no product/UI integration, no authority/capability widening, no serialized live handles, and no force-push of #228.
Keep draft until the remaining exact-head live-provider jobs complete green. Supersedes the stale implementation transaction in #228; #223 remains the canonical epic.