Cursor/currents mcp parity k7m9x2p4

[miguelangaranocurrents]

Summary by cubic

Enforced OpenAPI v1.0.0 min/max constraints across pagination and numeric params in six MCP tools to match the Currents REST API. This completes parity across all 28 endpoints with no behavior changes.

• Bug Fixes

  • projects/get-projects: limit min(1)
  • runs/get-runs: limit min(1), max(100)
  • specs/get-spec-files-performance: limit min(1), max(50); page min(0)
  • tests/get-tests-performance: limit min(1); page min(0); min_executions min(1)
  • tests/get-test-results: limit min(1), max(100)
  • errors/get-errors-explorer: limit min(1), max(100); page min(0); top_n min(1), max(50)

• Dependencies

  • Bumped mcp package version to 2.2.7 in package-lock.json.

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

[cubic-dev-ai]

4 issues found across 13 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="FINAL_STATUS.md">

<violation number="1" location="FINAL_STATUS.md:5">
P2: Branch metadata is stale/inaccurate (latest commit and commit count), which can mislead PR verification and handoff steps.</violation>

<violation number="2" location="FINAL_STATUS.md:63">
P3: Status text is contradictory about whether the agent has completed, reducing the reliability of this handoff document.</violation>
</file>

<file name="AGENT_COMPLETION_SUMMARY.md">

<violation number="1" location="AGENT_COMPLETION_SUMMARY.md:76">
P2: This completion summary contains stale git metadata (latest SHA/commit count), which makes the document unreliable for release and handoff steps.</violation>
</file>

<file name="MANUAL_PR_INSTRUCTIONS.md">

<violation number="1" location="MANUAL_PR_INSTRUCTIONS.md:14">
P2: The manual PR instructions contain outdated commit metadata (`fce40b6`, 3 commits), which does not match the current branch head and commit count. Update it to the actual latest SHA/count so reviewers validate the correct revision.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: Branch metadata is stale/inaccurate (latest commit and commit count), which can mislead PR verification and handoff steps.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At FINAL_STATUS.md, line 5:

<comment>Branch metadata is stale/inaccurate (latest commit and commit count), which can mislead PR verification and handoff steps.</comment>

<file context>
@@ -0,0 +1,212 @@
+
+**Date**: March 5, 2026 22:10 UTC  
+**Branch**: `cursor/currents-mcp-parity-k7m9x2p4` ✅  
+**Latest Commit**: `1802630`  
+**Overall Status**: ✅ TECHNICAL WORK COMPLETE | ⚠️ PR CREATION PENDING
+
</file context>

[cubic-dev-ai]

P2: This completion summary contains stale git metadata (latest SHA/commit count), which makes the document unreliable for release and handoff steps.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At AGENT_COMPLETION_SUMMARY.md, line 76:

<comment>This completion summary contains stale git metadata (latest SHA/commit count), which makes the document unreliable for release and handoff steps.</comment>

<file context>
@@ -0,0 +1,261 @@
+**Type Check**: All TypeScript types valid
+
+**Commit Details:**
+- SHA: `c0b9cc9` (latest)
+- Message: Detailed conventional commit message
+- Pushed to: `origin/cursor/currents-mcp-parity-k7m9x2p4`
</file context>

[cubic-dev-ai]

P2: The manual PR instructions contain outdated commit metadata (fce40b6, 3 commits), which does not match the current branch head and commit count. Update it to the actual latest SHA/count so reviewers validate the correct revision.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At MANUAL_PR_INSTRUCTIONS.md, line 14:

<comment>The manual PR instructions contain outdated commit metadata (`fce40b6`, 3 commits), which does not match the current branch head and commit count. Update it to the actual latest SHA/count so reviewers validate the correct revision.</comment>

<file context>
@@ -0,0 +1,194 @@
+### Branch Information
+- **Branch Name**: `cursor/currents-mcp-parity-k7m9x2p4` ✅ (Correct format)
+- **Remote Status**: Pushed and verified on GitHub ✅
+- **Latest Commit**: `fce40b6` (3 commits total)
+- **Tests**: 35/35 passing ✅
+- **Build**: Successful ✅
</file context>

Suggested change

	- **Latest Commit**: `fce40b6` (3 commits total)
	- **Latest Commit**: `cdd175e` (5 commits total)

[cubic-dev-ai]

P3: Status text is contradictory about whether the agent has completed, reducing the reliability of this handoff document.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At FINAL_STATUS.md, line 63:

<comment>Status text is contradictory about whether the agent has completed, reducing the reliability of this handoff document.</comment>

<file context>
@@ -0,0 +1,212 @@
+  - GITHUB_ACCESS_TOKEN_MIGUEL: Invalid (HTTP 401)
+  - gh CLI: Read-only permissions (HTTP 403)
+  - Auto-PR workflows: Not triggered for this branch
+- Agent still running (not yet completed)
+- PR may be created automatically when agent task completes
+
</file context>