update-versionslisted

# Update pinned upstream versions Several playbooks hardcode an upstream release version in a play var (`marklessVersion: "0.9.6"`, `ouchVersion`, `rescrobbledVersion`, `nvm_version`, `darktable_version`, `rapidraw_version`, `art_version`, `displaylink_version`, `evdi_version`, `cudnn_version`, …). These pins drift as upstream ships new releases. This skill reviews the drift and helps apply bumps safely. The playbook is always the single source of truth for the current value — the review script reads the pin straight from the file, it is never duplicated. ## Step 1 — Review drift (always start here) Run the review script from the repo root: ```bash "${CLAUDE_PROJECT_DIR}/scripts/check-pinned-versions.bash" ``` It prints a table of `PINNED` vs upstream `LATEST` and the status of each pin, and exits: - `0` — every pin matches upstream latest (nothing to do). - `1` — one or more pins are behind, or a manual pin (cuDNN) needs a human. - `2` — hard error (e.g. `gh` missing/unauthenticated, or the manifest has drifted from the playbooks — fix the manifest row it names). Report the outdated pins to the user and confirm which ones to bump before editing anything. Bumping every dependency at once is rarely wanted — some are intentionally held back (a newer release may need a matching checksum, a new asset name, or a Fedora-version-specific build). ## Step 2 — Apply a bump (per pin, deliberately) For each pin the user agrees to update: 1. **Edit the version var** in its pl