Build coffee history and experiment workflows with Ask Bean Bro

docs/bean-bro-workspace.md

@@ -0,0 +1,20 @@
+# Coffee workspace and Ask Bean Bro
+
+The Planner now has a compact header, editable plan name, batch summary, annotated curve, contextual URL/curve actions, and an integrated Ask Bean Bro conversation. Mobile uses Plan / Ask Bean Bro tabs. Source URL and coffee name each occupy a full-width row; other basic coffee inputs use two columns. Timing calculations and explanations are expandable.
+
+## Plan → roast → taste → experiment
+
+- **Today** lists tasting reminders after three days, low green inventory below 500 g, unattached roasts, and experiments awaiting an outcome. These are disclosed reminder thresholds, not prescriptions about ideal rest or batch size.
+- **Coffee history** groups by linked green inventory lot, otherwise by the entered coffee name. Unnamed plans stay separate. It shows plan variations, favorite batches, quick tasting feedback, detailed cupping links, and two-batch measured-curve comparisons. Histories are searchable and paginated; waveform data loads only for selected comparisons.
+- **Experiments** capture a question, one change and an expected cup result. Quick tasting records balance, sweetness, favorites, and whether the experiment improved the cup. Favorites reflect the user's preference, not model grades.
+- **Ask Bean Bro** saves its recent conversation with each plan, uses only that account's matching coffee history, and returns reviewable before/after proposals. Applying or creating a variation is explicit; stale proposals are rejected. Undo and plan history support recovery. Coffee facts and machine settings are outside the assistant's patch allowlist.
+- **Roast day** provides a timer and manual milestone recording in Fahrenheit. Records persist in the account-scoped local draft offline. When online, Finish & record tasting creates a finished roast once for that timer session. Manual records export as JSON and are labeled as sparse observations, not continuous telemetry. Importing an Artisan file extracts its measurements, opens the uploaded roast, and can suggest a name-based plan match for confirmation.
+- **Plan history** records meaningful changes transactionally. The latest 50 revisions are listed; revisions remain in personal/admin exports. Restore retains current inventory consumption, chat and roast-day records. New uploads, manual roasts and plan attachments capture plan targets; later plan edits do not rewrite those captured targets. Older records without snapshots remain clearly labeled as using the current linked plan. Past revisions or targets from before this release cannot be reconstructed.
+
+## Model configuration
+
+Admin → Bean Bro selects the configured provider/model for chat, prefill and finished-roast reviews. Test connection makes a small real request and reports the responding model. Provider credentials remain in the protected Pi configuration on the server. Auto follows the server model overrides and configured availability. Network-dependent assistance and cloud saves require connectivity; the roast-day draft remains available offline after the app shell has been cached.
+
+## Validation
+
+API regressions cover ownership, revision restore, scoped history/evidence, proposal allowlists, model connection permissions, idempotent manual completion, captured targets and exports. Chromium regressions cover plan switching, cloning, URL persistence, real print PDFs, chat persistence and reviewable edits, mobile tabs and field widths, offline reload with roast events, manual completion and coffee comparisons. Desktop/mobile screenshots were inspected and used to correct the layout.