Repository navigation
fix: reuse stable caches and record resource closeout (v6.6.3) - #102
Merged
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
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.
Repeated per-job Go caches and anonymous Docker volumes accumulated substantial
disk usage in the recent audit. Execution and closeout guidance now prefers stable
compatible caches, records isolation reasons and classifies persistent data. An
optional POSIX ledger attributes resources to jobs and reports conservative review
hints without running resource commands or deleting data.
Design and scope
See
docs/plans/2026-10-05-resource-lifecycle-design.md, its independent review,implementation plan and ADR0007. One PR/four tasks, all implementing commits present;
scope hash verifies. Related: #101 (bounded resource portion; other follow-ups remain).
Active, failed, unknown, reusable, database, volume and worktree resources remain
protected. Directory candidates require all declared owners to close successfully,
project temporary containment, no protected overlap/links/worktree markers, bounded
inspection and final path/identity validation. Session/job IDs are attribution,
not authentication. Stable locks and atomic JSON updates serialize cooperating
writers; corrupt/duplicate/future metadata is preserved.
Validation
and scan-swap issues. Nine mutation attacks and 96 concurrent operations passed.
Runtime transcript from the shipped helper and an owned temporary module:
Direct CLI/Go proof does not establish host callbacks or agent adoption. The helper
adds no lifecycle hook, quota, allocator, daemon or automatic cleanup. Candidates
require fresh live-use/data review and separate deletion authorization.
Release and installation
Use the existing main tag/marketplace workflow, then publish the verified official
v6.6.3 Release. Preserve active native6.6.1 installation and configuration until
the safe maintenance condition is satisfied; native updates can prune old paths.
Overall installation acceptance remains open. Rollback leaves resources and
metadata intact; existing caches need no migration.