feat(mcp): detect stale installs and API compatibility in doctor and status

[Crystora]

Summary

Closes #19

• Add stale install checks to gittensory-mcp doctor and gittensory-mcp status.
• Compare the local MCP package version against npm latest with semver-aware handling.
• Show exact upgrade guidance when stale: npm install -g @jsonbored/gittensory-mcp@latest.
• Show a no-install fallback: npx @jsonbored/gittensory-mcp@latest <command>.
• Add optional API compatibility checks from /health when minMcpVersion or minClientVersion is available.
• Treat npm/API check failures as warnings or unavailable states instead of hard failures.
• Redact tokens and local absolute paths from diagnostic output.

Validation

• npm run test:ci
• npm run changelog:check

Safety

• Backend-only change
• No secrets, wallet details, user PATs, raw trust scores, or private rankings exposed
• Public text avoids compensation-seeking or optimization-tactic language
• OpenAPI/MCP behavior updated where needed
• Public docs/changelogs updated where needed

[JSONbored]

PR #28 - feat(mcp): detect stale installs and API compatibility in doctor and status
Signal: REQUEST CHANGES

Required changes:

• Fix changelog freshness: CI fails at changelog:check.
• Do not rewrite packages/gittensory-mcp/CHANGELOG.md into a stale/unreleased shape; run the repo’s changelog command or remove manual changelog drift.
• Keep the implementation; the version/API compatibility approach is generally sound.
• Watch for conflicts with #27 because both modify packages/gittensory-mcp/bin/gittensory-mcp.js and mcp-cli tests.

[Crystora]

@JSONbored Fixed changelog.