Repository navigation
Complete pm-utd6 and add MCP compact projection integration coverage - #188
Conversation
Add explicit MCP integration assertions for pm_context, pm_plan, and pm_contracts compact/deep projection behavior so agent-facing payload guarantees stay stable while completing the active pm-utd6 + pm-8d00 workstream with refreshed dependency/docs and full verification evidence.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
@codex review\n/gemini review\n@gemini-code-assist review |
|
Warning Review limit reached
More reviews will be available in 50 minutes and 37 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThis PR adds integration test coverage for MCP tools ( ChangesMCP Integration Tests and Task Metadata
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
To use Codex here, create a Codex account and connect to github. |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
tests/integration/mcp-dynamic-package-actions.spec.ts (1)
783-870: ⚡ Quick winConsolidate duplicated pm_context depth test.
This test is nearly identical to lines 135-214 in
tests/integration/mcp-handshake.spec.ts. Consider extracting the shared test logic into a reusable helper function to reduce duplication and ensure consistency.♻️ Refactoring approach
Create a shared helper in
tests/helpers/:// tests/helpers/mcp-context-depth.ts export async function testPmContextDepthProjection(context: PmTestContext) { // Shared test logic here }Then call it from both test files:
it("defaults pm_context to brief depth and supports explicit deeper projections", async () => { await withTempPmPath(testPmContextDepthProjection); });🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@tests/integration/mcp-dynamic-package-actions.spec.ts` around lines 783 - 870, Extract the duplicated pm_context depth test into a shared helper function (e.g., testPmContextDepthProjection) and call it from both specs; move the shared logic that uses withTempPmPath, create CLI invocation, handleRequest calls for "pm_context", and the subsequent assertions into tests/helpers/mcp-context-depth.ts so both tests simply call await withTempPmPath(testPmContextDepthProjection); ensure the helper accepts the PmTestContext and performs the same assertions (checking brief default, deep option, id/title/status assertions) and references handleRequest and pm_context consistently.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@tests/integration/mcp-dynamic-package-actions.spec.ts`:
- Around line 783-870: Extract the duplicated pm_context depth test into a
shared helper function (e.g., testPmContextDepthProjection) and call it from
both specs; move the shared logic that uses withTempPmPath, create CLI
invocation, handleRequest calls for "pm_context", and the subsequent assertions
into tests/helpers/mcp-context-depth.ts so both tests simply call await
withTempPmPath(testPmContextDepthProjection); ensure the helper accepts the
PmTestContext and performs the same assertions (checking brief default, deep
option, id/title/status assertions) and references handleRequest and pm_context
consistently.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: 9a9450da-099b-4e9c-a0b7-debb96decfb9
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (11)
.agents/pm/chores/pm-8d00.toon.agents/pm/extensions/.managed-extensions.json.agents/pm/history/pm-8d00.jsonl.agents/pm/history/pm-98d1.jsonl.agents/pm/history/pm-jhr0.jsonl.agents/pm/history/pm-utd6.jsonl.agents/pm/tasks/pm-utd6.toondocs/COMMANDS.mdpackage.jsontests/integration/mcp-dynamic-package-actions.spec.tstests/integration/mcp-handshake.spec.ts
Extract duplicated pm_context brief/deep projection checks into a shared helper so both MCP integration specs stay consistent and future projection contract updates only require one test-logic change.
|
Pushed follow-up for CodeRabbit nitpick: extracted shared pm_context projection assertions into tests/helpers/mcp-context-depth.ts and reused in both integration specs.\n\n@codex review\n/gemini review\n@gemini-code-assist review |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
To use Codex here, create a Codex account and connect to github. |
Persist final merge evidence and closure metadata for the completed workstream so both tracker items are terminal with explicit resolution, expected/actual outcomes, and release records tied to PR #188.
Summary
pm-utd6execution work with refreshed evidence, docs clarification for optionalgovernance-auditdedupe-audit, and@sentry/nodedependency bump to^10.57.0pm_contextbrief/deep behavior,pm_plancompact-vs-deepshowprojection, andpm_contractsflagsOnlycompact command projectionpm-utd6,pm-8d00) with linked files/tests, manual smoke evidence, GH/Sentry/security snapshots, and full verification recordsTest plan
pnpm buildpnpm typecheckpnpm contracts:checkpnpm quality:staticpnpm quality:docs-linkspnpm security:scanpnpm audit --audit-level lownode scripts/run-tests.mjs test -- tests/integration/mcp-handshake.spec.ts tests/integration/mcp-dynamic-package-actions.spec.tsnode scripts/run-tests.mjs coverage(149 files, 2626 tests, 100% statements/branches/functions/lines)pnpm changelog:pm:checkpm health --check-only --summarypm validate --check-resolution --check-history-drift/tmp/pm-manual-smoke-pOHfet): init/create/list/update/comments/search/history/contracts/health/validate