updatelisted

# Updating the suite, and migrating the tree it serves Two jobs, in order: bring the **install** up to date, then bring the **adopted project** up to the conventions the updated suite expects. They are separable — a tree can need migrating under an install that is already current — and Job 2 is the one with teeth. **Project facts come from `.claude/WSS.WORKFLOW.json`** — or, on exactly the trees this skill exists for, from a manifest that predates that name. The authorities this skill answers to: - [`wss/workflow/WSS.MANIFEST.md`](../../wss/workflow/WSS.MANIFEST.md) — the `WSS.suite` stamp key and the current key set. - [`wss/workflow/WSS.NAMING.md`](../../wss/workflow/WSS.NAMING.md) — the file-naming convention with its "would this file exist if the suite were not installed?" test. **Both, not either.** A migration renames files *and* rewrites keys in one pass, and these are two contracts: reading only the key table leaves every rename unjudged. - [`wss/workflow/WSS.RECORD-CONTRACT.md`](../../wss/workflow/WSS.RECORD-CONTRACT.md) — what each record holds, the `- migrate:` line shape in the release list, and the never-rewrite rule for append-only records. - [`wss/workflow/WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md) — every write below that has an owner goes through it: the manifest (stamp included) through `manifest-writer`, commits through `git-writer`, records through their writers. ## Job 1 — update the install Say which form this machin