===

Spec-Up-T help
https://trustoverip.github.io/spec-up-t-website

Upgrade this repo (from 1.x, or from a script that still does
node -e "require('.../custom-update.js')"):

  npx spec-up-t@latest custom-update

You do not have to install 2.0.0 first.
npm update and the GitHubUi "Custom Update" button will not cross
from that old script onto 2.1.0. The old node -e require() does not
run the update.

After that command succeeds:
  npm run custom-update

The command prints a plan and asks before it writes. The plan lists
scripts, files, dependencies, .gitignore patterns, npm install, and
per-spec snapshot or legacy-dir changes.

  spec-up-t custom-update --dry-run            print the plan only
  spec-up-t custom-update --yes                apply without asking
  spec-up-t custom-update --force-workflows    replace workflows that differ

A workflow that differs from the boilerplate is kept. --force-workflows
replaces menu.yml, render-and-deploy.yml, and zenodo-update.yml. Run that
locally and commit. The GitHubUi button does not pass --force-workflows,
and GITHUB_TOKEN cannot push changes under .github/workflows/.

Upgrading to 2.2.0: GitHub Actions has no prompt. Until menu.yml
contains the line below, the GitHubUi Custom Update button prints
the plan and the job fails. Nothing is written.

  npm run custom-update -- --yes

Run once locally, then commit:

  npx spec-up-t@latest custom-update --yes

Or add that line to the custom-update case in menu.yml by hand.
After that commit, the button applies the plan.

When a Trust over IP spec repo should take an update is a working-group
decision (regular meeting, or sooner when a release must be applied).
The tool does not choose. See the website page "When to run custom-update".

===