fix(mcp): surface npm latest across ui

[oktofeesh1]

Summary

• Use npm dist-tags.latest as the shared current-version source for @jsonbored/gittensory-mcp UI display.
• Keep 0.2.0 as the explicitly labeled minimum-supported compatibility floor.
• Add a source audit so stale visible MCP version copy does not come back.

What changed

• Added a shared MCP package metadata helper for current version, install command, npm URL, and recent release history.
• Reused the shared source in the header badge, homepage, install panel, changelog, API overview, docs, and agent setup snippets.
• Updated install/setup snippets to use @latest or the resolved npm latest where appropriate.
• Added npm run ui:version-audit and wired it into test:ci.
• Updated the roadmap page to reflect roadmap: Gittensory ecosystem adoption v1 #127 and phase epics roadmap(phase 0): stabilize while shipping #233-roadmap(phase 5): ecosystem distribution #238.
• Replaced the hardcoded command-preview repo/PR with user-entered context.

Why

The site was mixing current MCP package display with compatibility metadata, which left visible 0.2 copy after npm latest moved to 0.3.0. Current version display should come from npm latest; compatibility metadata should stay scoped to /v1/mcp/compatibility and explicitly labeled minimum support.

Validation

• npm run ui:version-audit
• npm run ui:typecheck
• npm run ui:lint
• npm run ui:build
• git diff --check
• Browser checked Worker preview routes: /, /agents, /docs/quickstart, /docs/mcp-clients, /app/miner, /changelog, /roadmap, /api, /app/commands.

Notes

• /app/* inner panels are behind GitHub OAuth in production preview, so browser checks cover the signed-out boundary while typecheck/build/source checks cover the authenticated panel changes.
• The changelog still shows historical npm releases by design; the current release badge and page lead use dist-tags.latest.
• Touches feat(api): expose API and MCP compatibility metadata #86, roadmap: Gittensory ecosystem adoption v1 #127, roadmap(phase 0): stabilize while shipping #233, roadmap(phase 1): miner command center #234, roadmap(phase 2): maintainer trust and browser extension #235, roadmap(phase 3): repo owner intake console #236, roadmap(phase 4): adoption analytics and launch system #237, roadmap(phase 5): ecosystem distribution #238, feat(mcp): make doctor output a miner onboarding checklist #240, and docs(launch): create miner quickstart by contribution lane #252.

[dosubot]

Related Knowledge

3 documents with suggested updates are ready for review.

gittensory

Getting Started

View Suggested Changes

@@ -224,13 +224,13 @@
 ### Install
 
 ```sh
-npm install -g @jsonbored/gittensory-mcp
+npm install -g @jsonbored/gittensory-mcp@latest
 ```
 
 Or run it once without installing globally [[18]](https://gittensory.aethereal.dev/docs/quickstart):
 
 ```sh
-npx -y @jsonbored/gittensory-mcp --help
+npx -y @jsonbored/gittensory-mcp@latest --help
 ```
 
 ### Step 1 — Log in
@@ -456,7 +456,7 @@
 **Fix:** Run `gittensory-mcp doctor` — it checks whether your installed version matches npm latest and prints the exact upgrade command if you are behind [[42]](https://github.com/JSONbored/gittensory/blob/40c019c82d87568c232fbe7fabf50212e983075a/packages/gittensory-mcp/bin/gittensory-mcp.js#L844-L846). This is a known real-world issue [[43]](https://github.com/JSONbored/gittensory/issues/19). Upgrade with:
 
 ```sh
-npm install -g @jsonbored/gittensory-mcp
+npm install -g @jsonbored/gittensory-mcp@latest
 ```
 
 Or use the no-install fallback: `npx @jsonbored/gittensory-mcp@latest <command>`.

✅ Accepted

MCP & Agent Integration

View Suggested Changes

@@ -34,7 +34,7 @@
 Install `@jsonbored/gittensory-mcp` globally from npm. The package requires **Node.js 22.0.0 or higher** [[7]](https://github.com/JSONbored/gittensory/blob/1e7506f4c5226d0b9b5da8fcd219309d84bacfcd/packages/gittensory-mcp/README.md#L11-L18).
 
 ```sh
-npm install -g @jsonbored/gittensory-mcp
+npm install -g @jsonbored/gittensory-mcp@latest
 ```
 
 If you are working from a local checkout of the Gittensory monorepo, use the workspace link instead:

✅ Accepted

Overview & Concepts

View Suggested Changes

@@ -162,7 +162,7 @@
 
 **What it is:** A local stdio MCP wrapper — the first-class base-agent surface.
 
-**Install:** `npm install -g @jsonbored/gittensory-mcp`
+**Install:** `npm install -g @jsonbored/gittensory-mcp@latest`
 
 The `@jsonbored/gittensory-mcp` npm package is the primary integration point for coding agents and individual contributors [[30]](https://github.com/JSONbored/gittensory/blob/f63f125e2126dc58ac5a63e88f4f33d1e13b2979/README.md#L23). It inspects local git metadata and calls the Gittensory API without uploading source contents [[20]](https://github.com/JSONbored/gittensory/blob/f63f125e2126dc58ac5a63e88f4f33d1e13b2979/packages/gittensory-mcp/README.md#L3-L5).
 
@@ -286,7 +286,7 @@
 > **Quick install:**
 > 
 > ```sh
-> npm install -g @jsonbored/gittensory-mcp
+> npm install -g @jsonbored/gittensory-mcp@latest
 > gittensory-mcp login
 > gittensory-mcp doctor
 > ```

✅ Accepted

^{How did I do? Any feedback?}