v2.12.1

Patch release. No runtime changes — it fixes the release pipeline and re-aligns every published package on one version. npm packages had been silently stuck at 2.10.5 (2.11.0/2.12.0 were never published to npm: the registry rejected the re-upload with E403 and the workflow masked the failure). npm intentionally skips those versions and jumps 2.10.5 → 2.12.1.

Fixed

• Release workflow syncs npm package versions to the tag — publish-npm (surrealmemory), publish-sdk (@acidkill/surreal-memory-client) and publish-vscode run npm version <tag> --no-git-tag-version before building, so a stale package.json can never be re-published again (root cause: the pipeline bumped pyproject.toml/__init__.py but never the npm manifests)
• Publish failures are no longer masked — with a token set, a failed npm publish/vsce publish fails the job loudly; graceful skip only for a missing token or an idempotent re-run (exact version already live)

Changed

• integrations/surrealmemory, integrations/surreal-memory-client, vscode-extension manifests bumped to 2.12.1 to match published artifacts

Registry state after this release

• PyPI surreal-memory 2.12.1 ✅ · npm surrealmemory 2.12.1 ✅ · npm @acidkill/surreal-memory-client 2.12.1 ✅
• VS Code Marketplace / Open VSX / ClawHub: skipped — VSCE_PAT / OVSX_PAT / CLAWHUB_TOKEN secrets not configured

Full changelog: https://github.com/acidkill/surreal-memory/blob/main/CHANGELOG.md#2121--release-pipeline-npm-packages-actually-ship-again