4.1.26

chore(release): sync the version constants with 4.1.26

`scripts/bump-version.mjs` moves `package.json#version` and the
workspace package manifests, but the two SOURCE constants are written by
`sync-version` during the BUILD — `packages/peaks-loop-shared/src/
version.ts` (CLI_VERSION) and `packages/peaks-loop-internal-runtime/src/
index.ts` (RUNTIME_VERSION). The 4.1.26 bump was committed without a
build afterwards, so those two files still read 4.1.25 while the root
manifest read 4.1.26, and the version-parity gate failed on it:

  tests/unit/runtime/cli-version-lockstep.test.ts
    expected '4.1.25' to be '4.1.26'
  tests/unit/release/version-parity-gate.test.ts
    '::error title=CLI_VERSION drift::…'
  tests/unit/publish/lockstep-three-packages.test.ts

This is the same class the release workflow's own "Verify peaks-loop-shared
tarball CLI_VERSION parity" gate exists to catch — the gate was right and
the tree was wrong.

The 4.1.25 tag was NOT affected: its tree carried 4.1.25 in all three
places, so its publish was not blocked by a version drift.