[deep-report] Add remediation detail to terse MCP HTTP-transport config errors #65921

Description

pkg/cli/mcp_add.go returns two terse errors for HTTP-transport MCP server configs that state a failure without saying what's missing or what to provide:

• mcp_add.go:253: errors.New("HTTP transport requires URL configuration") — doesn't say which key is expected (url) or show an example.
• mcp_add.go:261: errors.New("HTTP transport requires configuration") — doesn't say a config block is expected at all, let alone its shape.

pkg/cli/secrets.go:40 has a similar pattern (errors.New("HTTP 403: access denied") with no remediation hint), surfaced by the same automated review. Only the two mcp_add.go sites are in scope here since they're mechanical and low-risk; secrets.go's message is paired with existing context (how the secret was being checked) so may need different wording — leave that to the implementer's judgment.

Expected Impact

Users debugging a broken MCP server config get actionable guidance (expected field name + example) instead of a bare "requires configuration" message, cutting trial-and-error round-trips.

Suggested Agent

Any coding agent (mechanical, low-risk Go error-message edit) — e.g. Copilot coding agent.

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport incremental cycle, 2026-10-05 ~18:4xZ — surfaced by Repository Quality: Error-Handling Contract Consistency (Task 3), narrowed to the two verified mcp_add.go sites after live source verification. Note: that report's Task 1 (string-matching in update_extension_check.go) was checked and found to be an already-justified (nolint/redacted):errstringmatch exception (Windows locked-binary detection via stderr text), not a defect — not filed. The model_aliases.go:57 capitalization claim was also checked and found to be the codebase's intentional BUG: assertion-prefix convention, not a style error — not filed.

Generated by 🔬 Deep Report · claude · agent · 169.3 AIC · ⌖ 8.97 AIC · ⊞ 7.1K · ◷

• expires on Oct 7, 2026, 10:43 AM UTC-08:00