Add caller-preset trust and protected composition - #1745
Draft
Zetazzz wants to merge 1 commit into
Draft
Conversation
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.
Summary
Implements F03 from constructive-io/constructive-planning#1693 as a reusable Graphile preset trust boundary:
base -> caller -> protectedpreset composition;extends, cycles, accessors, and malformed preset structure;Architecture boundary
The primitive receives its protected paths and plugin names from the owning server or feature. It does not hard-code scoped introspection, retirement, storage, WebSocket admission, or other future feature settings.
Caller preset activation remains intentionally dormant.
graphile.extends/graphile.presetare not wired into runtime configuration in this PR; safe activation must wait until F17 includes preset composition in the exact build/cache identity.This PR does not claim a direct performance improvement. It establishes the composition and trust contract required by later independently reviewable features.
Validation
pnpm install --frozen-lockfilepnpm --filter @constructive-io/errors test— 42 tests passedpnpm --filter @constructive-io/graphql-server exec jest --runInBand— 162 tests passedpnpm --filter @constructive-io/errors buildpnpm --filter @constructive-io/express-context buildpnpm --filter @constructive-io/graphql-server build— CJS and ESMpnpm --filter @constructive-io/perf-harness test— 7 tests passedpnpm --filter @constructive-io/perf-harness build— CJS and ESMgraphile.ts)git diff --checkExcluded