5 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude Opus 5.5	6836f61bd4	MAINT-13 round 3: provider site, hourly fixed-tariff check, faster tests ... - A price-provider site with no fixed tariff is not a gate (its plan never sets `cheap`); DECISIONS §3 says so and a test pins it. - The fixed-tariff check is worked out once an hour, not every tick. - test_maint13: run() steps really are `step` minutes; the long loops use 5-minute steps (the per-tick cap); wall backstop checked "not before". - test_safety93: the drain bound is the rig's configured drain rate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 12:03:55 +02:00
glenn schrooyenandClaude Sonnet 5.5	6f05b2e4be	MAINT-13 round 2: gate open when nothing holds the charge back; safety93 scenario restored ... - gate_open is true with no price gate set up, in a cheap window, or while the pack is taking charge; the stall rule and timeout now work on a no-tariff site. - reset the save timer on a phase change; exact 5 min gap-cap test. - test_safety93: original timeout scenario kept (B finished) plus a case where a due B takes the slot after A's failure. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bdqr7PiaHcBnzPituu2yTC	2026-10-08 10:29:46 +02:00
glenn schrooyenandClaude Opus 5.5	28eff568b5	MAINT-13: a full pack that stops at 98-99 % is not a failed charge ... A charge is complete at SoC >= target, or at >= target - 3 once the SoC has made no new high for 60 min of allowed charging, or when the charging time runs out at >= target - 3. The 36 h timeout counts only the minutes the price gate let the pack charge (plus a 7 day wall-clock backstop). A cycle that fails (stuck drain, charge below target - 3) backs off 7 days, tells the operator once (EN + NL), and no cycle starts on that pack in that time unless the operator forces one. State survives a restart; old state files load. No option added. DECISIONS/MAINT-13-full-pack-is-complete.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 09:36:06 +02:00
adminandClaude Opus 5.5	214051d1a8	SAFETY-93 review: a charge that ends by a stale link or a refusal hands back smoothly too ... A battery still in CHARGE but dropped by the allocator (stale link, or a SAFETY-73 refusal contradicting its charge) left its -2000 W in the loop's start point, and B went 0 -> -1600 W in one cycle. The end is now noted after the unit claims are filed: in CHARGE, live and not contradicted. Tests: part 6 (stale link, refusal) and a spy on the guard suspension. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-03 00:10:21 +02:00
adminandClaude Opus 5.5	05eb93f139	SAFETY-93: the maintenance charge end hands back smoothly, with no grid charging at a high house ... At N>=2, when a battery's maintenance charge ended, its watts stayed in the loop's start point and landed on the other battery (B 0 -> -1600 W in one cycle, charging from the grid at a 6000 W house). On the cycle a charge ends, the loop now starts from what the others stood at plus that battery's new command. N=1 and all identity digests unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-02 22:38:42 +02:00