| 1 | // Local-only — the MCP BROWSER-APPROVAL flow, the gap a code review found: |
| 2 | // `resume.$executionId.tsx` POSTed to the bearer-gated `/api/mcp-sessions/*` |
| 3 | // with no Authorization header, so standalone-web approvals 401'd. The existing |
| 4 | // approval scenario (selfhost/mcp-approve.test.ts) approves PROGRAMMATICALLY via |
nothing calls this directly
no test coverage detected