fix(mcp): align registry changes output schema

[JSONbored]

Motivation

• The MCP registryChangesOutputSchema declared field names (previous, current, added, removed, changed, warnings) that do not match the actual RegistryChangeReport returned by buildRegistryChangeReport, causing schema-aware MCP clients to reject or drop the real diff payload.

Description

• Update registryChangesOutputSchema in src/mcp/server.ts to advertise the actual fields returned: currentSnapshotId, previousSnapshotId, addedRepos, removedRepos, changedRepos, and summary.
• Add regression coverage to test/unit/mcp-output-schemas.test.ts to assert the tool gittensory_get_registry_changes exposes the corrected schema properties and no longer advertises the stale names.
• Seed two registry snapshots in the added test helper and assert the MCP tool call returns schema-valid structuredContent containing addedRepos, removedRepos, changedRepos, currentSnapshotId, previousSnapshotId, and summary.
• Files changed: src/mcp/server.ts and test/unit/mcp-output-schemas.test.ts.

Testing

• Ran TypeScript typecheck with npm run typecheck and it succeeded.
• Ran the focused unit test with npm test -- --run test/unit/mcp-output-schemas.test.ts --reporter=verbose and all tests passed (9/9).

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	3cd4de5	Commit Preview URL Branch Preview URL	Jun 04 2026, 10:41 AM