chore: untrack per-machine RepoSkein config (.mcp.json, opencode.json)

[mong-x]

Part of a workspace-wide sweep untracking the per-machine RepoSkein MCP config from every CellarNode repo.

.mcp.json and opencode.json were committed by the RepoSkein setup. They hold a local-dev Neo4j password (reposkeintest, a localhost throwaway) and absolute /Users/... machine paths, so they are per-machine and should not be tracked.

This PR:

• adds .mcp.json / opencode.json to .gitignore
• removes them from the index (git rm --cached); they stay on disk locally and are regenerated per machine by reposkein-mcp init

The committed RepoSkein graph under .reposkein/ is unaffected. Root cause fixed upstream in reposkein/reposkein#18 (init now gitignores these files going forward).

---

Summary by cubic

Stop tracking per-machine RepoSkein MCP configs by gitignoring .mcp.json and opencode.json and removing them from the index. These files contain absolute paths and a local Neo4j password, are regenerated by reposkein-mcp init, and .reposkein/ remains tracked.

^{Written for commit 9f81185. Summary will update on new commits.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 16 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9f3710bc-59ff-46a5-9520-0a4c75dffab2

📥 Commits

Reviewing files that changed from the base of the PR and between a1d5a0e and 9f81185.

📒 Files selected for processing (3)

• .gitignore
• .mcp.json
• opencode.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch marcus/reposkein-untrack-local-config

---

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Auto-approved: Stops tracking per-machine MCP config files; only .gitignore update and git rm --cached. No logic or infra changes.

Re-trigger cubic</sub>