[plan] Improve Go type consistency and safety

[github-actions]

Overview

This tracking issue covers improvements to Go type consistency and type safety based on the Typist analysis from Discussion #6020.

Source: Discussion #6020

Key Findings

The Typist analysis identified:

1. Critical: Duplicated MCPServerConfig type definition with incompatible structures
2. High Priority: Incomplete migration to ToolsConfig structured types
3. Medium Priority: Extensive use of map[string]any in frontmatter parsing

Planned Tasks

This work is broken down into focused, actionable tasks:

1. Consolidate MCPServerConfig type - Fix the critical duplicate type definition
2. Complete ToolsConfig migration - Finish the structured types work already started
3. Add frontmatter structure types - Reduce type assertions in configuration parsing
4. Improve runtime detection typing - Eliminate nested type assertion pyramids

Strategy

Following a gradual migration approach:

• Keep map[string]any at YAML parse boundaries
• Convert to structured types immediately after parsing
• Maintain backward compatibility where needed
• Test thoroughly after each change

References

• Analysis: 🔤 Typist - Go Type Consistency Analysis #6020
• Key files: pkg/workflow/tools_types.go, pkg/parser/mcp.go, pkg/gateway/gateway.go

AI generated by Plan Command for discussion #6020