The /api/sessions endpoint was filtering out orchestrator sessions, so the mobile app could never detect a running orchestrator. Now the API finds the orchestrator session ID before filtering and includes it in the response as orchestratorId. - Add orchestratorId to /api/sessions JSON response - Add orchestratorId to SessionsResponse type - Thread orchestratorId through useSessions hook - Use orchestratorId in OrchestratorScreen instead of searching sessions Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| e2e | ||
| screenshots | ||
| server | ||
| src | ||
| .env.local.example | ||
| .gitignore | ||
| next-env.d.ts | ||
| next.config.js | ||
| package.json | ||
| postcss.config.mjs | ||
| tsconfig.json | ||
| vitest.config.ts | ||