Allow existing Vault output directories in capacity accounting - #416
Merged
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
1 participant
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.
Capacity checks for an existing user-owned output directory on the configured Vault previously required a separate archive route for each operation. Admit those directories beneath the global backup root for capacity accounting, so preflight and reservations can use the shared filesystem budget without new per-operation policy entries.
Admission verifies the target directory and live Vault identity. Reservation acquisition rechecks target inode, ownership, symlink resolution, and filesystem identity under the ledger lock. Capacity admission does not grant source-copy, write, or cleanup authority. Existing archive execution routes retain their separate contract.
Validation: 1963 public smoke tests passed, including fixture-backed positive and negative Vault cases; instant validation graph and bootstrap doctor/render dry runs passed. A source CLI probe against the configured Vault completed preflights and a reservation/release without writing archive payloads. Refreshed the generated KAG family through owner preparation. Host installation is tracked separately from this source change.