snowspeeder/roast_command_center
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix New plan feeling like a no-op; add plan delete and why-panel collapse
Test and deploy / test-and-deploy (push) Successful in 1m34s
Details

Browse Source 
New plan reset the form correctly but left the Plans drawer open over
it, so the reset was invisible until the user closed the drawer
themselves. Now closes it immediately, matching selectPlan().

Also adds a delete button per plan in the Plans drawer (server route
already existed) - deleting the currently open plan resets to a fresh
blank one, matching New plan.

Why-panel teaching callouts ("WHY CULTIVAR SETS THE CLOCK" etc.) now
default collapsed instead of wall-to-wall expanded on first load, with
an "Expand all" button in the header on both the planner and cupping
pages. Persistence flips from tracking collapsed-vs-default-open to
expanded-vs-default-closed to match.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
This commit is contained in:
snowspeeder
2026-07-31 15:34:56 -04:00
co-authored by Claude Sonnet 5
parent 2237c199c1
commit 84ce75dc14
5 changed files with 100 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
public/index.html
+10 -7
View File
@@ -129,6 +129,9 @@
><span class="dot"></span
><span class="autosave-text">Not saved yet</span></span
>
<button id="btn-expand-why" type="button" class="ghost-btn">
Expand all "why" notes
</button>
<button id="btn-print" type="button" class="primary-btn">
Print
</button>
@@ -372,7 +375,7 @@
<section class="panel-card" id="sec-coffee">
<div class="panel-head"><h2>The Coffee</h2></div>
<div class="panel-body">
<details class="why-panel" data-why="sec-coffee" open>
<details class="why-panel" data-why="sec-coffee">
<summary>Why cultivar sets the clock</summary>
<p>
A roast plan is three durations laid end to end: drying +
@@ -543,7 +546,7 @@
</div>
</div>
<div class="panel-body" id="blend-body">
<details class="why-panel" data-why="sec-blend" open>
<details class="why-panel" data-why="sec-blend">
<summary>Why blends combine times, never temperatures</summary>
<p>
The drum has one heat setting and one clock — you cannot
@@ -615,7 +618,7 @@
<section class="panel-card" id="sec-process">
<div class="panel-head"><h2>Roast Target</h2></div>
<div class="panel-body">
<details class="why-panel" data-why="sec-process" open>
<details class="why-panel" data-why="sec-process">
<summary>Why processing moves development, not first crack</summary>
<p>
Processing changed the chemistry that browning starts
@@ -743,7 +746,7 @@
<section class="panel-card" id="sec-bean">
<div class="panel-head"><h2>Bean Condition</h2></div>
<div class="panel-body">
<details class="why-panel" data-why="sec-bean" open>
<details class="why-panel" data-why="sec-bean">
<summary>Why bean condition is worth seconds, not a new plan</summary>
<p>
Moisture, density and screen size change how much energy the
@@ -826,7 +829,7 @@
<section class="panel-card" id="sec-machine">
<div class="panel-head"><h2>Machine Plan</h2></div>
<div class="panel-body">
<details class="why-panel" data-why="sec-machine" open>
<details class="why-panel" data-why="sec-machine">
<summary>
Why the rate of rise must fall, and never touch zero
</summary>
@@ -994,7 +997,7 @@
<span class="phase-chip">during the roast</span>
</div>
<div class="panel-body">
<details class="why-panel" data-why="sec-roastlog" open>
<details class="why-panel" data-why="sec-roastlog">
<summary>Record what you observed, never what you planned</summary>
<p>
A planned milestone written into the log as though it
@@ -1136,7 +1139,7 @@
<span class="phase-chip">after cupping</span>
</div>
<div class="panel-body">
<details class="why-panel" data-why="sec-after" open>
<details class="why-panel" data-why="sec-after">
<summary>One change per batch — arithmetic, not patience</summary>
<p>
Move two variables and there are four possible