Rebuild printable roast plans and remove machine-based adjustments

server/evaluate-roast.js

@@ -17,6 +17,11 @@ Reply with EXACTLY one JSON object and nothing else — no markdown fences, no p
 Every key must be present. Ground every statement in the numbers provided; never invent readings
 that are not in the data. If the data is too sparse to judge something, say so in "concerns".
 
+Do not diagnose failure or promise cup character from total time, DTR, or turning point alone.
+Phase-average RoR cannot prove the absence of an instantaneous crash/flick. Distinguish preheat
+setpoint from charge BT; do not infer one from the other. Machine history is descriptive context,
+not a rule for modifying the plan. Recommend one supported change and state uncertainty.
+
 Schema:
 {
   "summary": string,          // 2-4 sentences: overall read of this roast