Repository navigation
Engine 369: bounded authorized Volume usage references - #158
Merged
chen21019 merged 1 commit intoNov 4, 2026
Merged
Conversation
chen21019
marked this pull request as ready for review
November 4, 2026 23:08
chen21019
deleted the
verification/orchestration-engine-369-volume-usage-20261105
branch
November 4, 2026 23:26
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.
Volume detail can now show up to 50 currently readable active or stopped container references from a native SQL read limited to 51 relationships. Current object/Key and role-schema visibility remain authoritative; inaccessible targets do not disclose identities/counts or synthetic audit events. Native scalar wrapping preserves safe persisted metadata, while transformed/create-only fields are excluded before access. Ordinary output filters, read audit, grants and deletion oracles are unchanged; completeness always remains unknown.
Ten focused Java methods cover SQL bounds, scopes, hidden resources, audit and scalar compatibility. The release registry preserves all 132 prior identities and adds these ten (142). Source-only C03 re-extraction has 449 inputs and the same 1396 tuples with zero semantic/grant delta. Version preparation updates only the established 89 POMs and four script defaults; published historical notes are preserved.
Local checks use existing cached dependencies and module-scoped classpaths. Required original Security/JDK25 and independent CodeQL checks are running. Matching Web 208 / bridge 0.2.10, artifact qualification and native acceptance remain pending. This PR does not claim runtime PASS or publication.