v0.129.0

Rename commits are left to changelog coverage, which now decides whether the closing message prints an entry line, and rewrite project-name refuses when a Go target's latest release is marked unrecoverable.

Context

rlsbl rewrite project-name and rlsbl monorepo rename-releasable no longer
mark their rename commits as autogenerated, so changelog coverage judges them
like any other commit. Each closing message prints its runnable
rlsbl changelog add --type breaking line only when coverage asks an entry for
that commit, derived from the same exemption and scope rules the
changelog-coverage check applies: a releasable rename whose tag format carries
{name} changes the publish workflow and needs one, while a name-only rename
touches only files rlsbl owns and needs none.

rlsbl rewrite project-name used to rename a project with a Go target without
recording a go-module-path event when its latest release was marked
unrecoverable. It now refuses before writing anything: rlsbl's record cannot
establish the Go module path that release published, and no command can
establish that honestly, so the refusal names none.

Fixes

• rlsbl rewrite project-name no longer marks its rename commit as autogenerated, so changelog coverage asks for the breaking entry the closing message prints (its runnable rlsbl changelog add line names that commit); the transition-record commit stays autogenerated.
• rlsbl monorepo rename-releasable no longer marks its rename commit as autogenerated, so changelog coverage decides whether that commit needs an entry. When it does (a {name} tag format, whose rename changes the publish workflow), the closing message prints a runnable (cd <member> && rlsbl changelog add ... --type breaking) line naming that commit, which clears it; a name-only rename touches only files rlsbl owns, needs no entry, and prints nothing about the changelog.
• rlsbl rewrite project-name now refuses, before writing anything, when there is a Go target and the latest release's archive is marked unrecoverable, instead of renaming with no go-module-path event: rlsbl's record cannot establish the Go module path that release published, so the event the rename must record cannot be written. The refusal names no command, because none can establish that commit honestly.