One system: post-roast observations (weights, colour, DTR, cup notes,
'one change next batch', disproof) now live on the uploaded roast
(actual_roasts.after, migration 011), edited on the roast detail view
with weights/DTR prefilled from the .alog itself. The planner's screen
section is removed (the print worksheet keeps its hand-fill copy), and
the lot 'last refine' suggestion reads the note from both the new home
and legacy plans, newest wins.
Every roast now downloads two ways: the untouched original .alog, and
an updated supplemental copy with the app's data written back as valid
Artisan fields (weight, beans, roastingnotes incl. the LLM review,
cuppingnotes incl. linked cupping score/flavors) — serialized as a
Python literal so Artisan's ast.literal_eval re-imports it.
Co-Authored-By: Claude Fable 5 <[email protected]>
- POST /api/roasts stores the original .alog verbatim (multiple per plan),
parses it server-side, and kicks off an async zero-tool Pi agent review
(grade, highlights, concerns, next-batch suggestions, plan-vs-actual)
- /roasts page: table of historical actual roasts with review summaries;
row detail renders the BT curve as SVG with the plan curve overlaid,
shows the full review, and offers original-.alog backup download,
re-evaluate, and delete
- Planner's Reference curve drawer gains a multi-file finished-roast
uploader that attaches to the open (synced) plan
- Failed reviews record the error on the row and are retryable via
POST /api/roasts/:id/evaluate (e.g. once a model is configured)
Co-Authored-By: Claude Fable 5 <[email protected]>