Skip to content

feat(debugging): add project issues DEBUG-311 - #546

Draft
jordienr wants to merge 4 commits into
mainfrom
jordi/debug-311-mcp-issues
Draft

jordienr wants to merge 4 commits into
mainfrom
jordi/debug-311-mcp-issues

Conversation

@jordienr

Copy link
Copy Markdown
Member

Problem

Studio now presents Issues, but MCP clients still discover Advisors and cannot filter grouped findings by severity.

Fix

Add get_issues with security, performance, and health checks, minimum severity filtering, grouped affected resources, and explicit incomplete-check coverage. Keep get_advisors callable with its existing contract while hiding it from discovery.

Uses the existing Management API endpoints. Persistent state, dismissal, history, and banned-IP signals remain follow-ups. Published ChatGPT metadata needs a new plugin submission to expose the new tool; existing frozen callers remain supported.

How to test

  • Call get_issues with a project ID, then with type: "security" and severity: "critical". Each matching issue retains every affected resource.
  • Verify unavailable health checks appear in checks rather than as clean results, including on scoped read-only connections.
  • Call legacy get_advisors directly and verify its original response remains available.
  • Independent verification: 920 unit tests passed with retries disabled and shuffled seed 11011; all 7 stdio integration tests pass against a fresh build. Build, TypeScript, and Biome pass. Focused behavioral mutations detected broken grouping, unavailable coverage, and filter wiring.

Also fixes a pre-existing order-dependent registry test: initialize SDK schemas before measuring repeated server creation, retaining the zero-growth assertion.

Linked issue: DEBUG-311.

The shuffled origin/main baseline registers two lazy MCP SDK schemas on the first connection. Initialize that connection before measuring repeated server creation so the zero-growth assertion remains independent of test order.
@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 42993558361

Coverage increased (+0.03%) to 98.102%

Details

  • Coverage increased (+0.03%) from the base build.
  • Patch coverage: 1 uncovered change across 1 file (240 of 241 lines covered, 99.59%).
  • No coverage regressions found.

Uncovered Changes

File Changed Covered %
packages/mcp-server-supabase/src/issues.ts 165 164 99.39%
Total (3 files) 241 240 99.59%

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 6458
Covered Lines: 6358
Line Coverage: 98.45%
Relevant Branches: 1393
Covered Branches: 1344
Branch Coverage: 96.48%
Branches in Coverage %: Yes
Coverage Strength: 275.91 hits per line

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants