GPT Review — Phase 2A Scaffold Prompt — 2026-05-13

Verdict

NOT APPROVED AS-IS. Approve Phase 2A intent, but the prompt must be revised before execution.

Main blockers

1. The prompt still treats Docker network/AgentData port as assumptions from prior sessions. Phase 2A must execute discovery first and must not rely on memory.
2. The nginx template is structurally unsafe as a future deploy artifact: log_format belongs in nginx http context while location belongs in server context. The current single file may not be valid depending on include context.
3. REST mapping remains placeholder. The code scaffold hardcodes /api/...; this must be generated/edited only after endpoint discovery proves the correct internal routes.
4. Internal AgentData route may differ from external nginx route. Backend logs have previously shown upstream /health while external route is /api/health; therefore /api/* cannot be assumed inside Docker.
5. The prompt includes write endpoint placeholders and probe language. Phase 2A must not execute write probes without explicit approval.
6. The MCP client import path fastmcp.client.transports.StreamableHTTPTransport may be version-dependent; report must include version and fallback.

Allowed next step

Run revised Phase 2A-Discovery only:

• container/network/port discovery
• read-only endpoint discovery
• FastMCP version/prototype check
• nginx include-context inspection only
• no public nginx route
• no ChatGPT connector
• no ENABLE_WRITE
• no write probe
• no secret printed

Required report

Print directly in chat:

• raw redacted docker discovery results
• confirmed internal AgentData base URL
• confirmed read endpoint mapping with status codes and response shapes
• FastMCP version and MCP client test feasibility
• nginx include-context findings and proposed split config plan
• whether Phase 2A-Scaffold can proceed