BASE · 2dd6cddbc3fc20a4c8a330dc7361750cccfe35e3 Real T3 server · fresh database · HTTPS test relay · OAuth/PKCE 1. OAuth discovery: { "issuer": "https://" } 2. Register + pairing approval + PKCE token: HTTP 200; scopes: orchestration:read orchestration:operate settings:write source-control:write 3. initialize + tools/list: OK Get an upload URL. POST the file's exact bytes to `relativeUrl` on this MCP server's HTTP origin, then send via `t3_thread_send_attachments` with the returned `attachmentId`. 4. prepare_upload (70 bytes): { "attachmentId": "pending-ce8024fe-8144-4095-afc3-eac2ec4d4e28", "relativeUrl": "/api/attachments/upload/", "expiresAt": 1794639407230 } 5. Standalone destination: MISSING uploadUrl; new URL(relativeUrl) throws Invalid URL 6. Upload using response alone: blocked (Invalid URL) Control using externally supplied origin + relativeUrl: HTTP 204 7. Send uploaded attachment to replay thread: { "threadId": "mcp:3641c89c-6026-4fe2-b1ca-dfe0da616bfa", "messageId": "mcp:78d2bee4-52ce-4287-832d-28d4e97f8b90", "runId": "run:thread:mcp%3A3641c89c-6026-4fe2-b1ca-dfe0da616bfa:ordinal:1", "status": "starting" } RESULT: bug reproduced: no complete upload destination