alvis
59c493323f
When fetchOrchestratorTip returned null (LiteLLM timeout, bad JSON, etc.) the recommender silently fell back to randomPolicy, serving a raw Todoist task with no rationale — explaining both reported symptoms. - Remove randomPolicy/signalToCandidate; return 204 when orchestrator fails so the UI shows "All clear" instead of a confusing Todoist task - Pass recent_tip through the stack (frontend → POST /recommend → fetchOrchestratorTip → ml/serving RecommendRequest → build_orchestrator_messages) so after snooze the LLM is instructed not to repeat the snoozed content Fixes #122 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
apps/web
Next.js PWA. Phase 0 scope: three pages.
| Route | Purpose |
|---|---|
/sign-in |
Google/Apple OAuth buttons. No form. |
/connect |
List of integrations (cards). Tap → OAuth. Tap connected card → disconnect. |
/ (tip) |
Pure black background. One tip centered. Tap gestures: done / snooze / dismiss. |
Design notes
- The tip page is the product. Treat it like a watch face.
- Zero chrome, no nav bar, no settings icon while a tip is showing. Long-press reveals actions.
- Offline-first: last tip is cached; reactions queued until reconnect.