68 The installed version is not the one the plan named

What people usually ask

Set up the project with <framework>.

What comes back

The current release is installed, then configured from an older version’s documentation, and the first run fails on a setting that no longer exists.

Ask this instead

plan.md names <framework> <version>. Before anything else, print the version the plan names beside the version the install command would fetch today.
Pin the version in the install command: pip install <framework>==<version>, or the same with npm install <framework>@<version>. After the install, print the installed version from the package manager, not from any documentation, beside the plan's version.
If the two differ, read the changelog between them and list every change that touches configuration, defaults or removed settings, with the release it came in. Write nothing to a configuration file until I have seen that list.

Attach: plan.md.

Why it works: The version on disk and the version in the plan are put side by side before any setting is written against the wrong one.