v2.1.0

Added

• releasing derives the SemVer bump from the repo (the [Unreleased] headings, or the commit types since the last tag) and publishes pre-releases with --prerelease; committing marks breaking changes with !.
• The invariants script checks that every step reference between or within the skills points to an existing numbered heading.

Changed

• releasing works in repos without a CHANGELOG.md: it writes the notes from the commits in the shape of the previous Release, and tags HEAD directly when there is nothing to bump. It also stops when no commit landed since the last tag, reads an ISO date from the shell, and bumps Node versions with npm version --no-git-tag-version.
• committing tightens only the current concern's CHANGELOG bullets, leaving the full pass over [Unreleased] to releasing. It writes each bullet just before staging its concern, reads untracked files in the comment pass and secret scan, skips the CHANGELOG where a repo has none, and writes the Co-Authored-By trailer into the message file.
• scaffolding-repos points to committing for why the CHANGELOG boilerplate stays English.

Fixed

• scaffolding-repos renormalizes line endings only after the scaffold commit and on a clean tree, so unrelated edits no longer land in the normalization commit, and never overwrites an existing .gitattributes.
• releasing publishes with --verify-tag, so a tag missing on the remote aborts the Release instead of gh tagging another commit, and edits the notes when a workflow already created the Release. It watches the triggered run by ID with --exit-status, which works in a non-interactive shell and fails on a failed run, and writes the release commit subject in the repo's language.
• committing retries a rejected push with --autostash, since a plain rebase refuses to run while other concerns sit unstaged, and returns to an up-to-date main after a merge.
• README: the intro no longer presents the manual copy as the install path.