openpetswithchatandmcp/docs/cursor_todos.md

Cursor Integration Todos

This checklist tracks Cursor implementation work. Each phase has an Oracle approval gate before moving to the next phase.

Phase 1A — Validation spike

• Validate strict JSON vs JSONC support in Cursor MCP config.
• Validate whether Cursor requires restart/reload after MCP config changes.
• Validate global/project precedence for duplicate mcpServers.openpets.
• Validate duplicate server behavior across scopes. Project priority is documented; UI duplicate behavior still needs smoke-test awareness.
• Validate documented stdio fields for Cursor MCP entries.
• Choose final command strategy:
  • direct @open-pets/mcp@VERSION, or
  • @open-pets/cli@VERSION mcp.
• Smoke test real Cursor MCP connection.
• Record validation results in docs/cursor-phase-1-spec.md and/or docs/cursor-integration.md.
• Oracle review/approval gate.

Phase 1B — packages/cursor core

• Create packages/cursor package.
• Add MCP entry builders.
• Add config path resolution helpers with explicit configPath, homeDir, and projectDir inputs.
• Add status/classification helpers.
• Add safe read helpers.
• Add safe write/remove helpers.
• Add OpenPets-only preview helpers.
• Add redaction helpers.
• Add package build/typecheck/test/check scripts.
• Add temp-file tests for missing/empty config.
• Add temp-file tests for installed/needs-update/conflict/invalid/error statuses.
• Add malformed schema tests.
• Add symlink/non-regular/oversized file tests.
• Add no-write tests for invalid/conflict states.
• Add explicit replace tests preserving unrelated config.
• Add backup and atomic write tests.
• Add redacted preview tests, including recursive and case-insensitive redaction.
• Run package checks.
• Oracle review/approval gate.

Phase 1C — CLI integration

• Add @open-pets/cursor dependency to CLI if CLI consumes shared helpers.
• Add cursor to accepted configure agents.
• Implement project-local default behavior matching existing configure semantics:
  • no --cwd → process.cwd()/.cursor/mcp.json;
  • --cwd → <cwd>/.cursor/mcp.json.
• Do not add global CLI behavior unless explicit --global is designed and reviewed.
• Print target path, status, OpenPets-only preview, backup path, and restart/reload note.
• Ensure unrelated Cursor config secrets are never printed.
• Add CLI contract tests.
• Run CLI/package checks.
• Oracle review/approval gate.

Phase 1D — Desktop Agent Setup

• Add @open-pets/cursor dependency to desktop if desktop consumes shared helpers.
• Replace Cursor “Soon” card with active config-status card.
• Add Cursor detail pane.
• Add pet selector.
• Add install/update/replace/remove/refresh/copy-preview actions.
• Use global ~/.cursor/mcp.json only in desktop Phase 1.
• Show warning that Cursor may need restart/reload.
• Show warning that published npx mode may need npm/network/cache access.
• Show warning that OpenPets edits only mcpServers.openpets.
• Bind preload actions.
• Add desktop contract checks.
• Run desktop checks.
• Oracle review/approval gate.

Phase 1E — Full verification and docs

• Run pnpm check.
• Dogfood Cursor MCP setup locally.
• Update validation log in docs/cursor-phase-1-spec.md.
• Update public docs/website only after real Cursor smoke succeeds. (Deferred to separate web task.)
• Confirm package/release plumbing:
  • scripts/release-npm.mjs publish order if needed;
  • desktop packaging contract;
  • package dependencies;
  • workspace build/check inclusion.
• Oracle final review/approval gate.

Later phases — not Phase 1

Phase 2 — Cursor rules

• Draft Phase 2 rules spec in docs/cursor-phase-2-rules-spec.md.
• Oracle review before implementation.
• Run/record Cursor rules validation spike.
• Implement @open-pets/cursor rules helpers.
• Add CLI project-local rules install/update/remove flow.
• Add desktop rules preview/copy guidance only, unless separately reviewed.
• Run package and full checks.
• Oracle final review/approval gate.

Phase 3 — Cursor hooks

• Run hook validation spike first.
• Record payload fixtures and semantics.
• Oracle review before implementation.

Phase 4 — Cursor extension/plugin

• Research extension distribution.
• Oracle review before implementation.