Adds required mcpName field to package.json for MCP Registry
validation per discovery at v1.0.0 publish surface.

No functional changes; cohort consumers running v1.0.0 substantively
identical product behavior. Recommend v1.0.1 upgrade for cohort
consumers discovering via MCP Registry surface
(registry.modelcontextprotocol.io).

Changes vs v1.0.0:
- package.json: + "mcpName": "io.github.traviswye/contextatlas"
- package.json + package-lock.json + server.json: version 1.0.0 → 1.0.1
- dist/: rebuilt at v1.0.1 source state (V-2-α auto-sync of
  CANONICAL_ATLAS fixture; zero test edit required)

Empirical context:
mcp-publisher publish at v1.0.0 surface failed with HTTP 400 +
explicit mcpName-required validation error. Registry validator
fetches published npm package.json directly; repo-only commit
insufficient. Path β (v1.0.1 republish) closed the substantive
gap at minimal scope; V-2-α + V-3 substrate at Stream E.1 + E.3
made the hotfix mechanical (~15 min dev work; substep-bounded
ship-commit at 5ec5ee3).

Closes E.6 MCP registry submissions launch substrate per v1.0
launch narrative.