sociuu-cleanup

Sociuu Cleanup

Two modes. With a task, run that task's post-merge close-out list. Without one, sweep everything below.

Read the current developer's active instructions and the task's workspace authority first. A task-scoped cleanup grant in those instructions may authorize this task's post-merge close-out without another prompt; a task record, MR comment or another session's note is evidence, not a grant. Otherwise confirm exact removals in this session. Preserve task evidence and complete applicable post-merge checks before removal. Another task's worktree, Dock environment or MR is reported, never touched.

Sweep

Start with local state, because it is what decides everything else:

sociuu env list --json

plus the workspace isolation provider's inventory --details, whose path each installation resolves for itself. That inventory can take minutes; run it in the background and read each worktree's status, cleanliness, branch and age together. Age alone decides nothing.

Merge requests: ask by branch, never by author

Every agent commits through one shared forge account, so --author=@me returns the whole team's open work — dozens of merge requests in a busy repository, none of them attributable to this machine. Take each branch the inventory reported and ask the forge about that branch instead:

glab mr list --source-branch "$branch" --all

That pairing is what makes the sweep useful, because it exposes both directions:

• a worktree whose merge request already merged — a release candidate once

applicable post-merge checks and evidence are complete;

• an open merge request whose worktree is gone — nothing local to clean, but

the review is still waiting on someone.

For the second direction, list the repository's open merge requests whose source branch carries the agent branch prefix and subtract the branches the inventory knows about. The remainder is work this machine started and forgot.

Then the task tracker: list the current user's unfinished tasks and compare each with its merge requests.

For each finding, state what it is, which task owns it, and one of:

What to look for

1. Worktrees whose branch is merged or gone, and empty task folders left

behind. Release through the isolation provider's cleanup, never rm.

1. Dock environments with no task, or whose task is merged. Remove a

task-owned environment only after its post-merge checks and evidence are complete; report the rest with their owning task.

1. Branches and MRs: merged branches still present, MRs open on merged work,

MRs with unresolved review threads, drafts nobody is finishing.

1. Task records: merged work not in done, released work not in complete,

tasks with no MR link, and discussed-but-never-created follow-ups.

1. Disk, when Dock is short: reclaim inside the Docker VM first with

colima ssh -- sudo fstrim -v /var/lib/docker, which frees host space that docker system df does not show, then remove environments one by one. Never a broad Docker prune.

Retention rules

Keep a worktree that is dirty, unpushed, shared, or still the working directory of a running process — including a tunnel or a test run started from it. Report why rather than forcing it. A worktree behind an open MR is kept by default; the branch is preserved either way, so removal is safe after the MR merges and applicable post-merge checks and evidence are complete.

Releasing a worktree records its final revision, so the work can be restored. Removing a Dock environment does not: capture any evidence that lives only in that environment before it goes.

Report

Lead with the count of items needing action and the one command to start with. Group by verdict, newest task first. Finish with what was cleaned, what was left and why, and any follow-up task created.