release: CLI v0.6.3 + extension v0.1.8

[George-iam]

Summary

Combined release bump:

Track	Old	New	Tag to push
CLI (axme-code binary)	0.6.2	0.6.3	v0.6.3
VS Code / Cursor extension	0.1.7	0.1.8	extension-v0.1.8

CLI bump is PATCH (one bug fix, no new features). Extension bump is PATCH — it bundles the new CLI (the fix lives in server.ts, which the extension build inlines), no extension-side code change.

What ships — the only change since v0.6.2

#155 — axme_save_memory / axme_save_decision empty-args reliability.

Two independent agent sessions hit axme_save_memory failing with "expected string, received undefined" on every required field (args arrived empty {}). Verified not a server/handler/schema defect — every call whose args actually reached the server persisted, and save_decision worked in the same session. Root cause: client-side generative slip (tool-call shell emitted without composing the heavy free-text fields), amplified by an over-generalized "batch axme calls in parallel" habit from the read-tool instructions.

The MCP SDK validates before our handler, so echoing received keys would require loosening the advertised schema (worsening the root cause). Three text-only mitigations instead — no schema loosening, no behavior change for valid calls:

1. Custom zod v4 { error } messages on the required fields of both save tools — each says it is REQUIRED, must be composed in the same call, and that an empty/deferred emission is the usual cause. (Replaces the bland "received undefined" that the first agent misread as "the server lost my args" → 9× retry → false server-bug report.)
2. Hardened tool descriptions — "call standalone, not in a parallel batch; include all required fields in the same call" + a worked example arguments object.
3. Clarified server instructions — parallelism is for the READ tools only; a new SAVE-TOOL RULE for the write tools.

Full entry in CHANGELOG.md.

Test plan

• npx tsc --noEmit clean
• npm run build + npm run build:extension clean (extension reports v0.1.8)
• npm test — 613/613 (one flaky concurrent-lock subtest passed on rerun; unrelated)

After merge — push the two tags

The agent cannot push tags (safety hook). From a clean checkout of updated main:

git checkout main && git pull origin main

# CLI release → fires release-binary.yml (6 platform binaries + npm publish + plugin-repo sync)
git tag v0.6.3
git push origin v0.6.3

# Extension release → fires publish-extension.yml (5 platform .vsix → Open VSX + GitHub Release)
git tag extension-v0.1.8
git push origin extension-v0.1.8

Reminder from the last release cycle:

• Merge this PR BEFORE pushing tags — tags must point at the merge commit on main (last time we tagged before merge and both workflows built the old version).
• npm publish needs the Classic Automation NPM_TOKEN (not a granular/2FA token) — already fixed in the secret as of v0.6.0.

Watch: https://github.com/AxmeAI/axme-code/actions

🤖 Generated with Claude Code