4 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude Opus 5.5	bc6d744c6c	SAFETY-83 review: banked month peak and no false alarm during a drain ... test_safety83 part 1: under a month peak banked above the limit the drain is lifted to peak - margin, and a drain the guard raises (steady or with 5 s spikes that saturate it) gives no 'Load too high' alarm; the part 3 overload still does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-30 13:41:47 +02:00
adminandClaude Opus 5.5	56cafefa79	SAFETY-83: a refiled peak floor stays under a safety SET, graded directly ... Kills M5 (refiled at P_SAFETY) on its own sentence, not only through the per-cycle claim check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 22:52:52 +02:00
adminandClaude Opus 5.5	3f69c174af	SAFETY-83: grade the refile at its boundary, and N=2 on its own ... A floor exactly at the drain rate stays at P_PEAK (kills `lo >= rate`), and part 4's N=2 check no longer shares its failure list with N=1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 22:50:46 +02:00
adminandClaude Opus 5.5	d77f1b1fdf	SAFETY-83: peak guard outranks the maintenance drain at N=1 ... At N=1 the drain is the site SET at P_MAINTENANCE (60), so the peak floor (P_PEAK, 50) was not applied and the house imported what the drain left. Where the floor asks for more than the drain rate, main.py now refiles the peak claim at P_MAINTENANCE, so it wins; safety SETs still park everything. Nothing else changes: safety78_identity --diff against 35cdffe changes only cycles where the guard wanted more than the drain; N=2 is byte-identical. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 22:40:14 +02:00