updatelisted

You are running `/update` in the **current working directory's repo**. Goal: bump the template `ref`, apply the sync, and open a PR with **nothing but template-owned files** in it. **Only files that come from the template repository may be touched.** The sync records exactly which paths it materialized in `.rhiza/template.lock`'s `files` list, and `plugin/scripts/stage_synced.py` (step 7) stages precisely that set — so the guarantee is mechanical, not something this prose has to be trusted to honour. **Never `git add --all`** and never fold in unrelated edits: no reformatting of the repo's own source, no dependency changes, no test fixes. Anything outside the set stays in the working tree and gets reported. **No gates, no scorecard, no issues.** `/update` syncs; `/quality` scores. Don't run `make test`/`make lint`/`make fmt` here — `make fmt` in particular would rewrite the repo's own files and break the rule above. Point the user at `/rhiza:quality` in the report instead. Argument (optional): `$ARGUMENTS` — an explicit template version tag like `v1.2.0`. If empty, use the template's latest release. Work through these steps. Stop and report if a precondition fails. ## 1. Preconditions - **`uv` first.** `Read` **`${CLAUDE_PLUGIN_ROOT}/prompts/install-uv.md`** and follow it before anything else (in a source checkout, `plugin/prompts/install-uv.md`). It's a one-line no-op when `uv` is already present. The sync runs through `uv run --python 3.12`, so if `uv --version`