Describe the existing ACL fixture adapter boundary #20
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/rootd!20
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/acl-fixture-contract"
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?
Describe the Integration-owned ACL workload through the existing explicit writable VFS route. The adapter retains its bounded effects and receives no additional grant or selector.
Refs #1 and erix/integration#65. Depends on #19.
This branch also includes the completed downstream features from #64.
WIP: Describe the existing ACL fixture adapter boundaryto Describe the existing ACL fixture adapter boundaryMerged the approved downstream work from #64. The upstream PR retains its own remaining scope and completion requirements.
Review uses the prepared history on #19. It preserves the completed #64 feature and its signed merge boundary, alongside the ACL documentation. The original branches remain unchanged.
Authenticated source admission precedes explicitly selected path mapping. Four fresh complete artifacts from two independently captured operations agree at 271824 bytes with no private source paths; the separate standalone mode retains its exact 271808-byte result. Cross-mode bindings are rejected. The component checks are complete; release-image and guest acceptance remain separate.