[deep-report] Docs: mcp-gateway.md mixes JSON and TOML config examples with no explanation #60033

Description

docs/src/content/docs/reference/mcp-gateway.md mixes JSON and TOML configuration syntax inconsistently within the same formal spec document. Section 4.1.1 (~line 163) states the gateway MUST accept configuration via stdin in JSON format, with all reference-table field names in camelCase (payloadDir, payloadPathPrefix, agentId). But Sections 4.1.3.2 (~line 330), 4.1.3.3 (~line 363), and 4.1.3.9 (~line 640) show configuration examples in TOML syntax with snake_case fields (payload_dir, payload_path_prefix, agent_id), with no explanation distinguishing when TOML applies vs. JSON, or that it represents a different consumer (e.g. the mcpg CLI's local config file, referenced only once at line 639).

Expected Impact

Prevents an operator from copy-pasting a TOML snippet into a JSON-only gateway config and hitting an unexplained parse failure — a real risk in a document that positions itself as a formal W3C-style spec.

Suggested Agent

Documentation-focused agent (e.g. docs-noob-tester/delight) or a maintainer doing a small docs PR.

Estimated Effort

Quick (< 30 min) — add one clarifying note before the first TOML example (~line 328) explaining it's the mcpg CLI/local config format, distinct from the JSON stdin payload the gateway process itself reads; or convert the TOML examples to JSON if they represent the same configuration surface.

Data Source

DeepReport Intelligence Briefing analysis, 2026-09-10 cycle, sourced from Delight User Experience Analysis Report #59999 (verified via direct read of the referenced doc sections; not previously filed as an issue).

network:
  allowed:
    - defaults
    - "api.anthropic.com"
    - "proxy.golang.org"

Generated by 🔬 Deep Report · claude · agent · 239.2 AIC · ⌖ 12.5 AIC · ⊞ 12.8K · ◷

• expires on Sep 12, 2026, 10:39 AM UTC-08:00