chore(release): bump workspace version to 0.3.4

Metadata-only release: ships the server.json packageArguments fix
(the serve subcommand the registry entry never declared) to the MCP
Registry, which rejects duplicate versions — so the fix can't ride
0.3.3. Also corrects publish-mcp-registry.yml's stale claim that a
same-version metadata re-push is possible.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: Your Name

.github/workflows/publish-mcp-registry.yml

@@ -6,9 +6,13 @@ name: Publish to MCP Registry
 #      Registry automatically. The registry validates that the npm package
 #      at `version` already exists, which is why it's chained *after*
 #      npm-publish, never racing it.
-#   2. workflow_dispatch — kept for manual re-pushes (e.g. re-registering a
-#      version whose metadata changed) without cutting a new release. Run
-#      with: gh workflow run publish-mcp-registry.yml -f version=0.2.0
+#   2. workflow_dispatch — kept for manually publishing a version the release
+#      train missed (e.g. the train failed after npm-publish). Run with:
+#      gh workflow run publish-mcp-registry.yml -f version=0.2.0
+#      NOTE: the registry rejects an already-registered version outright
+#      ("cannot publish duplicate version" — verified live 2026-07-19), so a
+#      server.json metadata fix can only ship with the NEXT version's publish,
+#      never as a re-push of an existing one.
 # Either accepts the version with or without a leading `v` (the release
 # train passes the raw tag, e.g. `v0.2.0`); the job strips it.
 on:

Cargo.lock

@@ -17,7 +17,7 @@ members = [
 # version against the downloaded release binary's real `--version` output
 # and treats any mismatch as a corrupted/wrong download, so a stale value
 # here silently defeats the verified-download fast path for everyone.
-version = "0.3.3"
+version = "0.3.4"
 edition = "2024"
 license = "MIT"
 rust-version = "1.85"