2026-03-22 — Serve experience end-to-end + hardening

What shipped

The serve-don’t-show experience is now end-to-end functional. The session started with #152 (serve UI) — rewriting /today as a four-state machine: energy check-in → serve one chunk → work with timer → feedback → next chunk or done. This replaced the old cycle-planning model entirely. Energy tracking (#159) was prepped and shipped next, wiring the energy budget from check-in through to the serve endpoint’s stop condition. The feedback loop followed: #164 added a text input between Done/Not now and the API call, and #165 re-ingests not-done feedback through the AI parse pipeline server-side to create new actionable chunks.

Two scout runs identified and prioritized 10 issues across dead code, security, error handling, performance, and UX. All 10 were executed in the same session. The old cycle-planning code (616 lines across 6 files) was removed (#177). Rate limiting was applied to all 5 AI-powered API endpoints (#178). The serve UI got proper error feedback instead of silent failures (#179). Prerequisite chain enforcement was added to the serve endpoint (#180). A gold “+” button was added to the nav for quick task ingestion (#181).

The second scout round focused on performance and polish. Missing database indexes were added for the serve hot path (#187). getTodaysCompletedCount was fixed to filter at the database level instead of loading all tasks into memory (#188). Stripe routes got error handling (#189). The show_timer config was wired to the working view (#190). The day-complete screen was enriched with energy context and stop reason (#191).

Completed

• #152 — Build serve UI: single chunk display with start/done/not-now
• #159 — Track energy spent and stop serving when budget exhausted
• #164 — Add feedback text input to active session done/not-done flow
• #165 — Re-ingest not-done feedback through parse pipeline
• #177 — Remove dead cycle-planning code (6 files)
• #178 — Add rate limiting to AI-powered API endpoints
• #179 — Add error feedback for failed API calls in serve UI
• #180 — Enforce prerequisite chain in serve endpoint
• #181 — Add “add tasks” shortcut to app navigation
• #187 — Add missing database indexes for serve hot path
• #188 — Fix getTodaysCompletedCount to filter at database level
• #189 — Add error handling to Stripe checkout and billing portal routes
• #190 — Wire show_timer config to working view
• #191 — Enrich day-complete screen with energy and mode context

Release progress

March 2026: 0 open / 0 closed (milestone exists but no issues assigned)

Carry-over

• #86 — Replace in-memory rate limiter with persistent solution (backlog)
• #101 — Branded emails (blocked)
• #108 — BCC founder on transactional emails (backlog)
• Source system integration (Asana/Jira/Notion outbound sync) — PRODUCT.md’s biggest unfulfilled promise, needs product design decisions
• Dashboard conflicts with serve-don’t-show model — shows task counts and queue links, needs design rethink
• Silent Supabase failures in completeTask cascade — 4 sequential unguarded DB operations, needs broader error-handling strategy

Risks

• The serve hot path now makes more queries (prereq check added, energy check parallelized) — indexes help but should monitor latency in production
• Defer re-ingestion calls the AI parse pipeline synchronously — slow for users when providing detailed feedback

Flags and watch-outs

• 14 PRs merged to main in one session — deploy to production and smoke-test the full serve flow
• The old sequencing API route and all cycle-planning components are deleted — any external references to /api/sequencing will 404
• daily-plan.ts was significantly trimmed — only getTodaysCompletedCount and getRemainingEnergy remain