Version inconsistency between pyproject.toml (0.1.2) and server.json (0.1.1)

[SteveGJones]

Summary

pyproject.toml:7 declares version = "0.1.2". server.json:6 declares "version": "0.1.1". The two should match (or both derive from a single source of truth).

Reproduction

$ grep -A1 '^\[project\]' pyproject.toml | grep version
version = "0.1.2"

$ grep '"version"' server.json
  "version": "0.1.1",

Why this matters

Downstream consumers pinning a paperbanana version (e.g. paperbanana>=0.1.2 in an integration that needs a recent fix) will see one number in package metadata and a different number in the MCP server descriptor. Cosmetic but easily confusing, especially for MCP-directory listings that may key on server.json.

Suggested fix

Two reasonable options:

1. Manual unification (5-min fix): bump server.json to 0.1.2. Document a release-checklist line item that bumps both files together.
2. Single source of truth: have server.json read its version from paperbanana.__version__ (which itself reads from pyproject.toml via importlib.metadata) at server-init time. Slightly more code, never drifts again.

Context for filing

Surfaced incidentally during an integration spike. Trivial change; happy to PR.

[dippatel1994]

Thanks @SteveGJones. Confirmed: pyproject.toml=0.1.2 vs server.json=0.1.1. Will sync as part of the 0.2.0 release work (#216).