v0.124.1

Restore the strictspec pairing so status, unreleased, and changelog add run on a fresh install.

Context

strictspec 0.2.5 was published while rlsbl's committed validators were still
stamped 0.2.3. A generated validator calls require_runtime_version(GENERATED_BY)
at import and that pairing is exact, so every published rlsbl version resolved
the newer strictspec through its unpinned floor and then refused to import:
rlsbl status, rlsbl unreleased, and rlsbl changelog add all aborted with a
strictspec version pairing mismatch for anyone installing fresh. The repository
lock still held 0.2.3, so its own suite never saw the skew. This release
regenerates the validators against 0.2.5, raises the declared floor to match,
refreshes the lock onto the same runtime, and adds a test that reds whenever the
committed stamps and the resolved strictspec disagree.

Fixes

• strictspec pairing restored. rlsbl status, rlsbl unreleased, and rlsbl changelog add no longer abort with a strictspec version pairing mismatch error on a fresh install: the generated validators are regenerated against strictspec 0.2.5 and the declared floor now matches them.