Optional Team Directory Cleanup Command

A recent shift in session management quietly reshaped how teams live on after a session ends. By removing cleanup_stale_teams() from session_end.py, the system now preserves team and task lifecycles - good for continuity, but risky if old directories pile up. At 76 team folders over 41 days, the disk footprint grows slowly but steadily, already clocking in at 7.6MB. That’s less than a week’s worth of new teamwork for most - so urgent cleanup isn’t critical yet. Still, if clutter creeps in, a targeted command can restore control. Here is the deal: a clean, optional way to trim stale team folders before they overwhelm your workspace.

The core fix? Introduce /PACT:clean-teams - a manual cleanup tool to delete teams older than N days. Not automatic, but intentional. It fits into workflows like /PACT:worktree-cleanup, offering a one-time refresh or recurring batch prune. Think of it as a safety valve, not a daily chore.

Behind the scene, this reflects a cultural shift: users increasingly expect their digital workspaces to stay lean, not collect dust. A forgotten team folder from a closed project isn’t just space - it’s clutter that distracts. The cultural impact? Clean interfaces foster focus, and transparency around cleanup builds trust.

But here’s the elephant in the room: cleanup commands aren’t obvious. Most users don’t know to prune their own folders - until accumulation hits. And while cleanups are low priority now, relying on users to report issues risks backlogs. Safety first: always back up before deleting, and never auto-clean.

The bottom line: keep directories tidy, but don’t panic over small clutter. Use /PACT:clean-teams as a mindful housekeeping tool when needed - not a default. When does cleanup matter? When it slows your workflow, not just your storage. Are you keeping your digital workspace clean, or letting it quietly collect? That’s the question you should ask yourself.