updatelisted

# /specseal:update — take the release, and see what is in it Two commands in a fixed order, and one thing neither of them does: tell you what you are getting. Running them by hand answers "you are now on 0.12.0", which is a number, not a reason to restart. ## Procedure **1. Record what is running.** Read the `version` from `$CLAUDE_PLUGIN_ROOT/.claude-plugin/plugin.json`. This is the version this session actually loaded, which is the one the user is comparing against. **2. Refresh the marketplace, then install.** ```bash claude plugin marketplace update specseal claude plugin update specseal@specseal ``` Both, in that order. The first pulls the marketplace clone; the second installs from it. Running only the second reports *already at the latest version* against whatever the clone last knew — the failure is silent and looks like success. If the second command reports it is already current, say so and stop. There is nothing to restart for. **3. Name what changed.** Read `CHANGELOG.md` from the refreshed marketplace clone — `~/.claude/plugins/marketplaces/specseal/CHANGELOG.md` — and summarize every entry between the old version and the new one, oldest first. Lead each with what it changes for the user, not with the release number. Two kinds deserve to be called out on their own line, because a user who skips them gets surprised later: - **behavior that changes without being asked for** — a new gate, a gate that fires where it did not, anything that writes to their