Fix context cancel lifecycle violations in workflow + MCP inspect paths

[Copilot]

LintMonster flagged 6 contextcancelnotdeferred findings where cancel funcs from context.WithTimeout were not deferred immediately after creation. This updates the affected call sites to follow the required context lifecycle pattern without changing behavior.

• Workflow resolver: annotated tag peel timeout

  • Updated /pkg/workflow/action_resolver.go to defer peelCancel() immediately after context.WithTimeout(...) in the tag-peeling loop.

• Safe outputs: remote action YAML fetch timeout

  • Updated /pkg/workflow/safe_outputs_actions.go to defer cancel() immediately after timeout context creation in fetchRemoteActionYAML.

• CLI MCP inspect: operation-scoped contexts

  • Updated /pkg/cli/mcp_inspect_mcp.go at all reported ListTools / ListResources timeout contexts (stdio + HTTP paths) to defer cancellation immediately after context creation.

Example pattern applied:

opCtx, cancel := context.WithTimeout(ctx, MCPOperationTimeout)
defer cancel()

result, err := session.ListTools(opCtx, &mcp.ListToolsParams{})

[pelikhan]

@copilot the explicit cancel too

[Copilot]

@copilot the explicit cancel too

Addressed in 6c07037. I restored explicit cancel() calls at the affected sites while keeping immediate defer cancel() for lint compliance and panic-safe cleanup.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.