Description
The Typist Go Type Consistency Analysis (#26855) identified 4 critical naming conflicts — duplicate type names with different field sets and serialization tags across packages. The most severe is MCPServerConfig, which is defined twice with incompatible extension fields:
pkg/parser/mcp.go:33 — JSON tags for registry parsingpkg/workflow/tools_types.go:395 — YAML tags for workflow-facing definition
These conflicts cause real maintainability risk: developers reading one definition don't know the other exists, serialization behavior differs silently, and future refactors risk breaking one path while fixing the other. The Typist report identified 3 additional critical conflicts (not yet specified in this issue — the full report at #26855 contains all 4 cluster details).
Expected Impact
Eliminates hidden divergence between parser-layer and workflow-layer type representations. Makes the type hierarchy explicit and navigable. Reduces risk of silent serialization bugs when fields are added to one type but not the other.
Suggested Agent
The Typist agent or a Go refactoring agent with serena/LSP access. The task is to rename one of each conflicting pair (e.g., MCPServerConfig → MCPRegistryServerConfig in parser layer), update all call sites, and add a comment explaining the intentional split if both definitions must be retained.
Estimated Effort
Medium (1–4 hours): identify all 4 conflict clusters from #26855, propose rename plan, apply renames via LSP rename refactoring, validate compilation and tests.
Data Source
DeepReport Intelligence Briefing — Apr 17, 2026 (this run). Primary source: Typist Go Type Consistency Analysis #26855 (2026-04-17).
Generated by DeepReport - Intelligence Gathering Agent · ● 595.8K · ◷
Description
The Typist Go Type Consistency Analysis (#26855) identified 4 critical naming conflicts — duplicate type names with different field sets and serialization tags across packages. The most severe is
MCPServerConfig, which is defined twice with incompatible extension fields:pkg/parser/mcp.go:33— JSON tags for registry parsingpkg/workflow/tools_types.go:395— YAML tags for workflow-facing definitionThese conflicts cause real maintainability risk: developers reading one definition don't know the other exists, serialization behavior differs silently, and future refactors risk breaking one path while fixing the other. The Typist report identified 3 additional critical conflicts (not yet specified in this issue — the full report at #26855 contains all 4 cluster details).
Expected Impact
Eliminates hidden divergence between parser-layer and workflow-layer type representations. Makes the type hierarchy explicit and navigable. Reduces risk of silent serialization bugs when fields are added to one type but not the other.
Suggested Agent
The Typist agent or a Go refactoring agent with serena/LSP access. The task is to rename one of each conflicting pair (e.g.,
MCPServerConfig→MCPRegistryServerConfigin parser layer), update all call sites, and add a comment explaining the intentional split if both definitions must be retained.Estimated Effort
Medium (1–4 hours): identify all 4 conflict clusters from #26855, propose rename plan, apply renames via LSP rename refactoring, validate compilation and tests.
Data Source
DeepReport Intelligence Briefing — Apr 17, 2026 (this run). Primary source: Typist Go Type Consistency Analysis #26855 (2026-04-17).