docs: build-artifact reclaim spec + action tagline#1
Open
mixflavor wants to merge 2 commits into
Open
Conversation
…and locale Add functional regression guards for the paths that were only ever verified by hand: lf_scan's dead/likely-orphan/kept buckets (a live or com.apple item is never flagged as junk), to_trash multi-account routing (each account's item lands in its own Trash), restore undoing a leftovers sweep, the sweep's clean() delete semantics (real empties but keeps the dir; --dry-run deletes nothing), and ss_resolve_lang locale mapping incl. the Simplified-Chinese -> English fallback. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add docs/reclaim-spec.md proposing a two-layer model for reclaiming build output: fold fixed-location caches into the existing sweep, and add an opt-in 'reclaim' verb for in-project build artifacts gated three ways (gitignored + build pattern + sibling manifest). All deletion stays on the move-to-Trash + receipt + restore rail, with the rebuild command recorded as the recommended undo — one consistent trust promise, no asterisk. Add the 'Scan, Confirm, Trash, the delete is yours' tagline to the README, encoding the trust model: sheersweep only ever stages to the Trash; the one irreversible step (emptying it) is always the user's. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
2 participants
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
docs/reclaim-spec.md— a design spec (proposal only, nothing implemented) for reclaiming space from build output without betraying the "cleaner you can read" trust model.Scan · Confirm · Trash — the delete is yours.The reclaim spec in one breath
Two layers, drawn along the line the sweep already refuses to cross:
node-compile-cache, pytest, …) → fold into the existing sweep. Low ceremony, no new verb..build/node_modules/target/dist/.next) → a new, opt-inreclaimverb. Never folded into the sweep, exactly asuninstall/leftoversare separate.A directory is eligible only when all three gates pass — ① gitignored, ② known build pattern, ③ a sibling manifest (
Package.swift/package.json/Cargo.toml). Gate ③ saves the user who has a content folder literally nameddist.All three finders (
uninstall,leftovers,reclaim) feed one candidate model{ path, size, why_safe, undo, last_touched }through the same present → consent → move-to-Trash + receipt + restore core.reclaimadditionally records the rebuild command (swift build/npm install) as the recommended undo — one consistent trust promise, no asterisk.--stale 30dfilters to artifacts whose repo hasn't been touched in N days.Tagline
Encodes the trust model: sheersweep only ever stages to the Trash; the one irreversible step — emptying it — is always the user's.
🤖 Generated with Claude Code