fix(mcp): update GoodMemory install version

[hjqcan]

Summary

• update the GoodMemory install metadata and command from 0.5.1 to the current published 0.7.2
• state the packaged MCP runtime requirement precisely as Bun 1.3.14+
• refresh the source-review date

Why

The existing directory entry points users at an obsolete GoodMemory package version and an imprecise Bun minimum. This keeps the single source content entry aligned with the current npm release and packaging contract.

Validation

• pnpm validate:content:strict — passed for 1,386 content files; 24 existing warnings were outside this entry
• git diff --check

No visual or generated-file changes.

[JSONbored]

Verified every value in this diff.

installCommand   npm install -g goodmemory@0.5.1  ->  @0.7.2
prerequisites    Bun 1.3 or newer                 ->  Bun 1.3.14 or newer

0.7.2 is real (npm publish time 2026-08-02T06:10:37Z). 0.5.1 shipped 2026-07-07 and was 14 releases behind. The Bun bump is not a guess either — it comes straight off the package engines field:

0.5.1  {"bun": ">=1.3.0",  "node": ">=20.0.0"}
0.7.2  {"bun": ">=1.3.14", "node": ">=20.0.0"}

That is exactly how I want a version correction sourced.

Two things you should know, neither of which blocks this.

First, it is already behind again — npm dist-tags.latest is 0.7.4 as of 2026-08-13, and your own .well-known/goodmemory.json retrievalSource now declares 0.7.5 on the next tag. Nineteen releases in four months means a pinned installCommand will re-stale continuously. If you would rather stop chasing it, send me a follow-up that drops the pin.

Second, your retrievalSources still list the MCP registry endpoint, and that endpoint still reports 0.5.1 — it has never been updated past it. So this PR now sits above its own cited source. Worth pushing a registry update on your side so the two agree.

Merging as a strict improvement on what is there.

[hjqcan]

Thank you for the careful verification and for calling out both drift paths. I followed your suggestion in #5791, which removes the version pin from both install surfaces.

I also confirmed the registry mismatch directly: npm latest is 0.7.4, while the official MCP Registry endpoint still returns 0.5.1. The immutable v0.7.4 server.json passes mcp-publisher validate; publication now only needs the registry login to be refreshed. I have kept that unresolved boundary explicit rather than claiming the source is current. Thanks again for merging the strict improvement.