docs: attribute the write-ahead login work to 0.0.14 (WALM-649)

[harrymove-ctrl]

Three changelog statements are wrong. The write-ahead/reclaim work (#793) is credited under ## 0.0.13 but first ships in 0.0.14; the 0.0.14 entry never mentions the Streamable HTTP transport that shipped with it; and both changelog pages' frontmatter summaries name the previous release as the latest while their own bodies already open on the current one. This fixes all three. No code changes, no manifest changes.

Evidence: on dev,

packages/mcp/CHANGELOG.md:27   "- Persist the delegate keypair before sign-in hands the URL to the browser ... (#793)"  under ## 0.0.13
docs/mcp/changelog.mdx:31      "The latest MCP package release is 0.0.13."   body's first heading is ## 0.0.14
docs/sdk/changelog.mdx:31      "The latest TypeScript SDK release is 0.1.7." body's first heading is ## 0.1.8

The #793 code is commit 0c765a03, authored 2026-09-16T03:05Z. npm published 0.0.13 on 2026-09-15T08:50Z and 0.0.14-dev.0 on 2026-09-16T10:14Z, so that work could not have been in 0.0.13; the tarballs agree — tar tzf memwal-mcp-0.0.13.tgz | grep recovery is empty and 0.0.14-dev.0 carries dist/recovery.js. 0.0.13's prose summary paragraph in the docs copy carried the same claim, so that clause is dropped there too.

Impact: documentation only, but it misdirects. A 0.0.13 user reading this believes an interrupted sign-in reclaims its delegate key when that build cannot; these pages carry answer frontmatter written for AI search citation, so the wrong version is what gets quoted back.

Test: none — prose.

Open question for you, not fixed here: CHANGELOG.md is not in packages/mcp/package.json's files array, so none of this reaches the npm tarball; the same is true for the SDK. Whether to publish it is a release-policy call, so both manifests are untouched. scripts/verify-manual-sdk-release.mjs is also left alone — extending it to catch this class of drift is hardening, not this fix.

Several open PRs (#921, #931, #870, #873, #892, #902) append to these same changelogs and will conflict textually.

Closes #927

[harrymove-ctrl]

Merged origin/dev in after #921 landed — merge commit 2e7e46ed, no rebase and no force-push, so the existing review stays attached.

Three changelog hunks conflicted, across packages/mcp/CHANGELOG.md and docs/mcp/changelog.mdx:

• Under ## 0.0.14 — both sides kept. fix(relayer,mcp): return remember at accept and drop the failed-write report #921's unreleased note (launchers pin @mysten-incubation/memwal-mcp@0.0.14-dev.0 until 0.0.14 is on npm) comes first, then this PR's ### Added section for the opt-in Streamable HTTP transport (MEMWAL_MCP_TRANSPORT), then ### Fixed. They say different things, so neither was dropped.
• End of ### Fixed — fix(relayer,mcp): return remember at accept and drop the failed-write report #921's deletion applied, this PR's addition kept. The accepted-then-failed report bullet on memwal_recall is gone, since fix(relayer,mcp): return remember at accept and drop the failed-write report #921 removes that feature's code. The write-ahead bullet (persist the delegate keypair before sign-in hands the URL to the browser) stays and remains moved up out of ## 0.0.13 — that move is the point of WALM-649.
• docs/mcp/changelog.mdx answer: frontmatter — took fix(relayer,mcp): return remember at accept and drop the failed-write report #921's paragraph verbatim. This PR had edited one token, The latest MCP package release is 0.0.13. to ...is 0.0.14., and that is factually wrong: npm dist-tags are latest=0.0.13 and dev=0.0.14-dev.0, with no stable 0.0.14 published. fix(relayer,mcp): return remember at accept and drop the failed-write report #921's rewritten paragraph already states that correctly, so the one-token edit was discarded; this PR's real content is carried by the bullet above.

docs/sdk/changelog.mdx did not conflict and is unchanged from this branch.

A merge-tree dry run against origin/dev is now clean. These are prose files only, so there was nothing to test.

[ducnmm]

LGTM, changelog updates accurately reflect 0.0.14 features and fixes.