Refactor MCP update tool to call Go function directly with context support

[Copilot]

The MCP update tool spawned a subprocess for each invocation, adding overhead and preventing proper cancellation handling. This refactors it to call the Go function directly with full context support.

Changes

• Added context-aware function chain: Created UpdateWorkflowsWithExtensionCheckContext() and context-aware versions of all downstream functions (UpdateActionsContext, UpdateWorkflowsContext, RunFixContext, checkExtensionUpdateContext, createUpdatePRContext)

• Refactored MCP handler: Replaced execCmd() subprocess spawning with direct call to UpdateWorkflowsWithExtensionCheckContext(). Added captureStderr() helper to intercept console output for MCP responses.

• Backward compatibility: Original functions remain as deprecated wrappers calling context versions with context.Background()

• Cancellation support: Added context checks at key points throughout the update chain to respect MCP request cancellation

Example

// Before: spawning subprocess
cmd := execCmd(ctx, cmdArgs...)
output, err := cmd.CombinedOutput()

// After: direct function call with context
output, err := captureStderr(func() error {
    return UpdateWorkflowsWithExtensionCheckContext(
        ctx, 
        args.Workflows,
        args.Major,
        args.Force,
        // ... other params
    )
})

Thread Safety

• No global state dependencies (only logger instances)
• captureStderr() uses proper goroutine + channel synchronization
• Channel lifecycle explicitly managed (reader goroutine owns closure)

Original prompt

Refactor the MCP-server command implementation of the update tool so that it calls the Go functin directly instead of spawning a separate process. Ensure that it invokes the command with a context, avoids data races, and does not rely on any global objects.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.