seed-updatelisted

Update this copy's **machinery** from a newer seed at **`$ARGUMENTS`** (a seed checkout or an unzipped `mise run export` archive). If `$ARGUMENTS` is missing, ask for the path. Read `docs/UPDATING.md` first — it defines the machinery/content boundary. Then: 1. **Compare versions.** Read this copy's `.seed-version` (or `.claude-plugin/plugin.json` → `version`) and the source's version. If the source is the same or older, say so and stop. 2. **List machinery files** (from `docs/UPDATING.md`): `.claude/hooks/**`, the seed-provided `.claude/skills/{reflect,learn,distill,bootstrap-stack,seed-update}/**`, `scripts/**`, `.github/workflows/**`, `.devcontainer/**`, the MCP mirrors, and root config (`dprint.json`, `lefthook.yml`, `.editorconfig`, `.gitattributes`). For `mise.toml`, only the `[tasks.*]` blocks are machinery — **preserve the project's `[tools]` stack choices**. 3. **Diff each one** (source vs local). Show the user a concise summary of what changed per file. **Apply nothing blindly.** 4. **Never touch content**: `.claude/knowledge/*`, `.claude/rules/core-rules.md`, `src/`, `README.md`, and the project-specific parts of `AGENTS.md`. (The `<!-- BEGIN learned -->` block in `AGENTS.md` is fine to refresh via `mise run mirror-rules`.) 5. **Apply** the approved changes. Update `.seed-version` to the source version. 6. **Verify**: run `mise run doctor` and `mise run test-hooks`; report results. 7. If this is a git repo, commit: `chore(seed): update mach