A yes/no device endpoint that walks through a daily pipeline of habits, each with a predict → confirm pair integrated with Fatebook for calibration tracking.

Each day the pipeline resets at 2am PST (7am São Paulo) and presents habits sequentially:

1. yoga? (80%) → creates Fatebook prediction (80% if yes, 20% if no)
2. did you yoga? → resolves prediction (auto-advances if Atom Matrix detected yoga)
3. 18 burpees? (80%) → creates Fatebook prediction with today's goal
4. did 18 burpees? → resolves prediction
5. all done!

Endpoint	Description
GET /question	Current question text (plain text, ≤30 chars)
GET /yes	Answer yes, advance pipeline
GET /no	Answer no, advance pipeline
GET /reset	Reset to step 0
GET /status	Full pipeline state (JSON)
GET /responses	All logged answers (JSON)

habits.ts     — Habit definitions (add new habits here)
pipeline.ts   — Generic state machine, auto-advance, auto-resolve
fatebook.ts   — Fatebook API client (graceful skip if no key)
main.ts       — HTTP handler (backward compatible)
cron.ts       — 2:15am PST auto-resolve unconfirmed predictions as NO

Add an entry to the HABITS array in habits.ts. Each habit needs:

• id, label, forecast, tags
• getPredictText() — predict question (≤30 chars)
• getConfirmText() — confirm question (≤30 chars)
• getFatebookTitle() — full Fatebook question title
• checkAutoComplete() — optional auto-detection from external source

Add FATEBOOK_API_KEY to this val's environment variables. Get your key at https://fatebook.io/api-setup