codex-scoped-cleanup

Files (3)

• SKILL.md
• app-server.md · references/
• native-attachments.md · references/

SKILL.md (first lines)

# Codex Scoped Cleanup

Apply this procedure only in Codex and within the current cleanup authority.
Route cleanup through the authorized resource owner using supported host operations.

## Authority And Native Lifecycle

Record the selected resources, their owners, permitted operations, preservation requirements, and protected resources before cleanup.
Treat archive authority, permanent-delete authority, attachment retirement, and physical removal as separate scopes.
Require explicit human authority for permanent deletion of the exact affected scope.
Preserve any action-time confirmation required by the selected tool, even when broader cleanup is already authorized.
Do not infer Project, Session, or Chat deletion support from a Thread method.

Before cleanup inventory or lifecycle changes, read [Owner-mediated resource lifecycle](references/app-server.md) unless already loaded completely.
Use supported owner-controlled operations rather than editing authoritative SQLite, rollout files, or raw host state.
Do not restart shared services or terminate unrelated workers to evade ownership guards.
When an owner or supported operation is unavailable, preserve affected resources and report the exact limitation.
Keep temporary private identities, paths, payloads, and logs out of published instructions and shared reports.

## Git Preservation

Default to removing completed, unused resources when retained Git history preserves every required source change.
Verify reachability from a retained branch, tag, or snapshot ref.
A merged PR establishes preservation of its merged source changes.
Do not rely solely on dangling objects, expiring reflogs, or an unspecified remote copy.
Compare staged, unstaged, untracked, and required ignored content before removing a physical checkout.
Preserve unique source, configuration, runtime storage, and database data outside Git.
Preserve resources required for current work or continuation, even when their source is committed.
Remove redundant recovery copies without creating another complete backup.

## Scoped Activity

Evaluate each session or worktree independently.
The parent project's recent activity does not prove that a particular worktree remains in use.
Use the requested inactivity window when inactivity defines the cleanup scope.
Retire verified completed, unnecessary resources within explicit authority without adding an age delay after completed handback.
Do not treat recent timestamps alone as proof that a resource remains needed or is eligible for retirement.
Include session events, compressed rollouts, running descendants, and exact worktree consumers when checking activity.
Exclude the current session and running work.
Read the latest request and result before treating an idle session as completed.
Preserve unfinished, blocked, recurring, and explicitly retained work, including its continuation and recovery assets.
Inspect affected descendants and every resource owner before changing a parent container.
Stop when scope, descendant coverage, ownership, or preservation remains uncertain.
Completed, unused Git-backed worktrees and recovery copies need no additional age delay.
Preserve primary, shared, and pinned checkouts during generic task cleanup.

## Worktrees And Caches

Have the authorized owner use supported worktree lifecycle tools or Git's worktree commands rather than direct directory deletion.
Refresh ownership and working-tree state before removal.
Do not force removal to bypass unique dirty or untracked content.
Check exact process arguments, working directories, open handles, and active containers for the selected scope.
Remove only isolated, unused, reproducible cache or build leaves.
Preserve active shared caches and dependencies needed by current executions.
Before deleting a quarantined cache, verify its inode, owner, and device.
Adjust owned directory permissions only within the selected cache.
Removing a child also requires write permission on its parent.
Preserve hard-linked file contents and permissions shared with other checkouts.

## Thread Worktree Artifacts

Before changing Worktree Artifact connections, read [Native Attachment Cleanup](references/native-attachments.md) unless already loaded completely.
Treat physical checkout deletion and Thread attachment removal as separate operations.
Have the authorized owner use supported archiving for physical retirement that requires retained recovery state.
Have the owner use supported attachment removal for verified stale connections.
Remove dangling active connections after verifying their paths are absent and their payloads contain no recovery state.
Remove archived connections only after verifying preserved required content and no continued-use requirement.
An archived checkout's absence alone does not establish that its connection is obsolete.
Do not use the owning Thread's activity as a substitute for worktree-specific evidence.

## Acceptance

Obtain the owner's fresh lifecycle, attachment, and filesystem readbacks as separate evidence.
Verify removed connections through the owner's supported listing and confirm protected connections remain.
Check that selected paths and temporary quarantine directories are absent after physical cleanup.
Have the owner remove temporary payload copies, scripts, logs, and task-owned processes after verification.
Report attachment counts separately from physical disk-space changes.
Use measured volume availability rather than summing directory allocation as reclaimed space.
Report source checks, owner-mediated readbacks, actual mutations, and model adherence as distinct evidence.
Do not require production deletion to validate cleanup instructions.

From ririnto/workgraph, MIT.

More from ririnto/workgraph