Opportunity: derive and show each plant’s expected flower-finish / harvest window from the strain’s flowering_days (catalog already has it, e.g. Gelato=63d) – r

WHAT: The roster shows ‘W9 – 62d – Flowering’ (elapsed only). The catalog strain record already carries flowering_days (Gelato=63, plus height_cm and a ‘want’ profile). WHY: an operator wants the EXPECTED finish, not just elapsed days. HOW: compute expected_finish = flip_date + strain.flowering_days (autoflower: sprout + days); surface on roster/crop-scheduler/Overview/cockpit, labelled ‘expected (from catalog)’. FULL DEV-READY SPEC written 2026-09-10: docs/design/plan-harvest-window-2026-09-10.md – covers the data model (verified: /roster has sprout_date/stage/strain_id/plant_uuid but NO stored flip_date – the key gap; catalog has flowering_days+format), the flip-date source options (store + journal-backfill), the maths + autoflower branch, 8 honest edge cases (unknown->em-dash+reason, plausibility clamp, overdue, ranges), single-source-of-truth brain computation (to avoid the multi-view Want-band drift), the 4 SPA surfaces, a harvest-reminder alert extension, a test plan, and 3 open questions for the operator. Found live 8.2.0.