chore(release): registry-only bump to 1.3.2 (no npm publish)

[virtualsms-io]

What this is

A registry-only version bump: server.json's root version moves from 1.3.1 to
1.3.2 so the MCP Registry re-crawls and re-publishes the listing with the corrected
description (already merged to main in #7). No npm publish, no new tag, no GitHub
Release.

Why packages[0].version stays at 1.3.1

The registry does not require server.json's root version to equal
packages[].version — this is an officially documented pattern in the MCP Registry
docs: "Use Prerelease Versions for Registry-only Updates." It exists precisely for
this case: shipping a corrected registry listing (description, metadata) without
republishing the underlying package.

• 1,247 of ~4,000 live registry entries already have these two versions differ.
• npm's registry validation only checks mcpName ownership — it never checks version
  equality against server.json.
• The published npm package virtualsms-mcp@1.3.1 is unchanged, so there is nothing to
  republish. Bumping packages[0].version here would just be a pointer to a package
  version that doesn't exist yet.

Diff

One line, versus main:

-  "version": "1.3.1",
+  "version": "1.3.2",

(the root version field in server.json only — packages[0].version, package.json,
and .plugin/plugin.json are all unchanged from main, still 1.3.1)

Not done here (by design)

• No npm publish / scripts/publish.sh
• No git tag
• No GitHub Release
• No merge — this PR stays open for review