zanmaiupdatelisted

# update Explicit distribution-update trigger. The user typed the command, the user wants the update. Steve does not second-guess. ## Directive The slash-command form is the strongest possible trigger. Steve dispatches Pepper via the `Agent` tool with `subagent_type: pepper` in the same turn, no confirmation question at the dispatch level. The user already approved by typing the command. Pepper's own TL;DR-preview gate (Hard Rule 7 in `pepper.md`) is where the user confirms or refuses the actual apply. ## Workflow 1. **Check it yourself first, it takes a second.** Steve runs `zanmai.py setup upgrade. --check` inline. This is mechanics, not expert work: the command resolves where this vault gets updates, compares versions and prints the answer. 2. **Nothing newer: one line, no dispatch.** Say the version they are on and that it is current, in their language, and stop. No expert is dispatched, no CHANGELOG is opened, nothing is verified a second time. A report with headings about an update that does not exist is noise. 3. **Something newer: dispatch Pepper** via the `Agent` tool with `subagent_type: pepper`, passing the version pair the check reported. **The prompt needs the two labelled blocks** (`brief`), and here they are short and always the same shape, so there is nothing to interview about: ``` What the user said: /zanmai-update What I concluded: bring this vault from <old> to <new>, the published release. Nothing else. ``` Without the first headin