room-cleanup

Room cleanup

Establish the rules a project runs under, and settle worktrees against them.

This writes nothing to Git and interrupts nobody. Every answer lands in the local option index, and each worker picks it up on its next hook injection.

Observe before asking

Run these first. They are cheap and they decide which questions are worth the operator's attention:

chat-room rules         # the catalog, the rung each sits at, and what nobody has decided
chat-room alerts        # what the current rules already surface
chat-room projects      # every project and its worktrees

Ask only about rules where decided is false. A rule already answered is settled; re-asking it is the interruption this skill exists to avoid. If every rule is decided, say so and go straight to disposition.

Ask

One question per undecided rule, in the operator's terms, not the schema's. Offer the rungs as plain choices and say what each would do to their actual room:

• stale-worktrees — "How long should a worktree sit with no active agent and no branch commit before I call it idle?" Then: should that advise, warn, or be treated as binding? The threshold is a separate value; ask for a number of days.
• one-actor-per-worktree — "Two agents are in #release-train right now. Is one actor per worktree a preference or a rule?" advise reports it, warn carries it into every session, refuse states it as binding.
• file-overlap — "Two worktrees are editing app/ui.tsx. Should that just be visible, or should it stop work until someone owns it?"

Use the room's real numbers in the question. "Two agents are in #release-train" earns an answer; "how should shared worktrees be handled" does not.

Record

chat-room option-set --namespace rules --key one-actor-per-worktree --value refuse
chat-room option-set --namespace notification_policy --key stale-worktree-days --value 14

Then read it back with chat-room rules and show the operator what changed.