awb-session-closelisted

# Session close-out — close with certainty, not fear > **Announce on activation:** "Using awb-session-close — read-only audit first, then cleanup on your approval." The fear this removes: after a long session you can't remember whether work is committed, pushed, merged, or whether stale branches are piling up — so you close anxiously or comb git by hand. This skill answers one question against ground truth: **"is it safe to close this window, and what's left to clean?"** — then does the cleanup only after you say yes. ## The risk model (why some findings stop you and others only nudge) Everything turns on one question: **would closing the window LOSE this, or leave it mid-operation?** - **BLOCK** — uncommitted changes; commits not on any remote (or an *unmeasurable* unpushed count — unknown is not "safe"); an in-progress **rebase / merge / cherry-pick**; **detached-HEAD** commits (reflog-only). These are local-only or mid-flight; close and they are at risk. Verdict: *not safe to close yet*. - **WARN** — a **stash**, open PRs, and stale local branches. These persist on disk / are already on the server, so closing loses nothing immediately — they are hygiene (a stash is the classic *forgotten* one), surfaced with the exact command. This is the whole point of the skill: scream only at real loss, stay quiet about the rest, so the warning never becomes noise you learn to ignore. ## Process 1. **Audit.** Run the tool. It is read-only **to your work** — it never co