Skip to content

feat(mcp): expose nested execution metadata in parse_mode (#1312)#1327

Merged
JeremyDev87 merged 1 commit into
masterfrom
taskmaestro/1775301252/pane-1
Apr 4, 2026
Merged

feat(mcp): expose nested execution metadata in parse_mode (#1312)#1327
JeremyDev87 merged 1 commit into
masterfrom
taskmaestro/1775301252/pane-1

Conversation

@JeremyDev87

Copy link
Copy Markdown
Owner

Summary

  • Add executionPlan and teamsCapability optional fields to ParseModeResult in keyword.types.ts
  • Inject TeamsCapabilityService into ModeHandler to resolve runtime Teams capability status
  • Build ExecutionPlan from dispatchReady agents: simple subagent plan or nested subagent+teams plan when Teams is enabled
  • Serialize execution plan via serializeExecutionPlan() for JSON-safe response
  • All new fields are optional — fully backward compatible

Closes #1312

Test plan

  • PLAN mode includes teamsCapability status (default: disabled)
  • PLAN mode with included_agent includes executionPlan with strategy: "subagent"
  • Teams enabled builds nested plan with strategy: "subagent+teams"
  • No executionPlan when no dispatchReady agents
  • TeamsCapabilityService failure handled gracefully (no crash)
  • Config-based Teams enablement reflected in teamsCapability.source
  • All 79 mode.handler.spec tests pass
  • All 5956 workspace tests pass
  • TypeScript strict mode — zero errors

@JeremyDev87 JeremyDev87 added feat mcp-server apps/mcp-server labels Apr 4, 2026
@vercel

vercel Bot commented Apr 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
codingbuddy-landing Ready Ready Preview, Comment Apr 4, 2026 11:52am

Add executionPlan and teamsCapability fields to ParseModeResult.
ModeHandler now injects TeamsCapabilityService, builds an ExecutionPlan
from dispatchReady agents, and includes Teams runtime capability status
in the parse_mode response. Nested plan (subagent+teams) is built when
Teams coordination is enabled. All new fields are optional for backward
compatibility.
@JeremyDev87 JeremyDev87 force-pushed the taskmaestro/1775301252/pane-1 branch from 99156c7 to b9ca0d0 Compare April 4, 2026 11:50
@JeremyDev87 JeremyDev87 merged commit 2aff4ac into master Apr 4, 2026
26 checks passed
@JeremyDev87 JeremyDev87 deleted the taskmaestro/1775301252/pane-1 branch April 4, 2026 11:53

@JeremyDev87 JeremyDev87 left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review: ✅ APPROVE

CI Status: ALL PASS (26/26 including circular-check)

Code Quality:

  • ParseModeResult extended: executionPlan? and teamsCapability? fields added
  • mode.handler.ts: TeamsCapabilityService injected, execution plan + capability status surfaced in PLAN/EVAL modes
  • execution-plan.types.ts: New dedicated types file — breaks circular dep cleanly
  • InnerTeamsSpec: Added to execution-plan.types.ts for TaskmaestroAssignment
  • Circular dep fix: agent.types uses local Mode alias, re-exports from execution-plan.types
  • All spec files updated: mode.handler, abstract-handler, mcp.service

Architecture:

  • Clean amend — single commit with all fixes included
  • Rebase conflict with PR #1321 resolved (InnerTeamsSpec + re-export merged)

Checklist:

  • CI ALL PASS (circular-check passes)
  • No unused imports
  • Backward compatible (new fields optional)
  • Clean git history (amend, no fix commits)

✅ Nested execution metadata exposed in parse_mode responses.

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

Labels

feat mcp-server apps/mcp-server

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(mcp): expose nested execution metadata in parse_mode and MCP responses

1 participant