update-to-latestlisted

# update-to-latest The recurring half of the versioned-standard mechanism. `align-to-standards` adopts the standard the first time; **this** brings an already-aligned repo up to the standard's latest - the way you'd bump a dependency, not re-scaffold from scratch. The target is always latest, never a pin: `.standards-version` is a bookmark of where the repo got to, not a version it is held at (ADR-025). Updating reads the **delta** between the tree the repo last aligned to and latest, applies only what changed, and proves the result with `self-verify`. ## Preconditions - The repo has a `.standards-version`. If it does not, this is a first adoption - use `align-to-standards` instead (which writes it). ## Steps 1. **Find the tree this repo aligned to.** Read `provenanceCommit` from `standard.manifest.json` - the standards repo commit this repo last aligned to. That commit, not a version string, is what the delta is measured from. **If the field is absent or null** (a repo aligned before it shipped), back-fill it once: resolve `.standards-version` to the commit that cut it - `git log --format='%h %s' -- VERSION` in a checkout of the standards repo, then `git show <commit>:VERSION` to confirm which version a commit carries - and use that. It is a one-time approximation, and it is approximate on purpose: since the standard's own PRs bump PATCH by default (R25), `main` carries unreleased change under a version number that has not shipped, so a versi