Add expiring artifact delivery outbox#1
Merged
Conversation
jugol
marked this pull request as ready for review
July 16, 2026 04:56
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.
What changed
artifactctlfor fixed seven-day delivery packages, inspection, and permanent expiry cleanupSessionStarthook and an hourly local scheduleroutput/entries have not been reviewed and migratedWhy
Generated deliverables were accumulating beside durable agent state without a reliable lifecycle. This makes
output/explicitly temporary while preserving exact files only through the existing, approval-gated private-vault workflow.Impact
Agents now deliver files with an exact expiry timestamp. There is no keep marker or caller-selectable extension. Existing pre-policy output is never silently enrolled, and publication checks prevent delivery artifacts from entering Git.
Validation