fix(mcp): point repository and docs at the real GitHub repo

[tobydoescode]

Problem

mcp/package.json and mcp/README.md both referenced github.com/tpettit/apple-bridge, which does not exist:

$ gh api repos/tpettit/apple-bridge
{"message":"Not Found","status":"404"}

The git remote is tobydoescode/apple-bridge.

This is live on npm. @evoio/apple-bridge-mcp@1.0.0 is already published, and its metadata currently reads:

repository.url = 'git+https://github.com/tpettit/apple-bridge.git'
homepage       = 'https://github.com/tpettit/apple-bridge#readme'

Both links on the npm page dead-end at a 404.

Fix

-    "url": "https://github.com/tpettit/apple-bridge"
+    "url": "git+https://github.com/tobydoescode/apple-bridge.git"

Plus the two prose links in mcp/README.md, which pointed at the same 404.

Only the repository field needed correcting — npm derives homepage and bugs from it when they're absent, so all three links resolve once this is published. Also normalised to the canonical git+https://...git form.

author: "tpettit" left as-is — that reads as a name, not a wrong handle.

Verified

• gh api repos/tobydoescode/apple-bridge → tobydoescode/apple-bridge
• npm pkg get repository → git+https://github.com/tobydoescode/apple-bridge.git
• No tpettit/apple-bridge references remain in any tracked .md or .json

Note

This is metadata only — nothing ships in dist, so the npm page won't update until the next publish. Worth doing before then rather than after.

🤖 Generated with Claude Code