Repository navigation
feat: shared resource catalog and fenced module GC - #57
Merged
Merged
Conversation
Feargin
marked this pull request as ready for review
October 21, 2026 17:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a shared resource catalog for signed modules: API 0.13, schema 52. Durable owner references, reservation of physical files before writing and publication after a durable close rule out the deletion of resources in use based on the local state of a single process. GC is allowed by the core under the protection of reader/backup pins; dependencies are kept until all physical variants are successfully unlinked. A deletion failure is retried, generations protect against repeated publication. Reader/backup get read-only access.
A module receives a frozen bound port without access to the DB pool, namespace and the internal deletion admission. Bootstrap after the first rollout and a logical restore keep GC closed until a full reconciliation. The first rollout requires stopping the old writers; the limitation is reflected in ADR 0089 and the wiki in the supported languages.
Checks of the exact d7a5f82:
The full verify/release of the Pro consumer 1ae09ec passed: 17 tasks, 66/66 full-parity verdicts, 10 000 crash trials and 11 244 failures without errors; this PR does not assert readiness of a stable production release. Only shared extension points enter the public code.