1 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude Opus 5	a991438e40	TARIFF-13: the coverage figure beside the peak stops resetting at a restart ... The capacity-tariff status row printed a peak read from SQLite next to a count of banked quarters read from PROCESS MEMORY - `PeakTracker.recorded`, an `int` set to 0 in `__init__` and counted up inside `sync()`. A 40-hour soak caught what that means at a driven restart, on both instances independently: before: 2026-09: peak 365 W, set by the quarter at 2026-09-11T18:45:00+00:00 - 10 % of the 3500 W soft limit; 120 quarter(s) banked after : 2026-09: peak 365 W, set by the quarter at 2026-09-11T18:45:00+00:00 - 10 % of the 3500 W soft limit; 0 quarter(s) banked Reproduced here before anything changed, through the real Controller and a real restart - a second Controller object against the same file on disk - at 12 -> 0 with 12 rows standing in `quarter_blocks`. The peak is durable and was never wrong. The COUNT is what says how much of the billing month that peak covers, and 365 W over 120 quarters and 365 W over 0 quarters are different claims about the same number. Mid-month, after every restart, the page made the weaker claim while displaying the stronger one's value. That is TARIFF-01's own argument - an unreadable store must not read as a zero peak, because a zero peak is disarming - one column over. `PeakStore.banked_count(month)` asks the database, and `recorded` is a property over it. Two more defects in the same variable fell out once it was driven, and neither was in the ticket: it was never scoped to a MONTH (on 1 October the row still showed September's tally beside October's empty month - measured), and it missed the block `restore()` banks from the checkpoint, which never passes through `sync()`. ⚠️ NOT 0, AND NOT None, WHEN THE STORE WILL NOT ANSWER. `banked_count()` returns None and the row renders `an unreadable number of quarter(s) banked`. `f"{None} quarter(s) banked"` was rejected because it reads as the same zero. `0 quarter(s) banked` stays true and reachable - it is what a month nothing has been written to says, and the two are asserted to be different text. ⚠️ THE DEDUPE IS NOT REMOVED WITH THE COUNTER. `_seen` still stops `cycle()`'s once-a-second `sync()` re-banking a block `P1Ingest.blocks` keeps for a day. The check that graded it asserted `recorded == 1` - the dedupe and the figure reporting it were the same variable - and now grades `sync()`'s RETURN, because counting rows cannot see a re-bank at all (PRIMARY KEY no-op). THE TIE RULE, DECIDED RATHER THAN EMERGENT: at equal wattage the EARLIEST quarter keeps the attribution. No bill and no guard moves - `peak_w` is still only ever raised, the `>` term is untouched, SAFETY-07 reads the same watts. The two readers DID disagree: the upsert's strict `>` kept whichever tied block was WRITTEN first while `recompute_month()` has always kept the earliest, the same only while blocks arrive in time order, and measured to diverge (09:45 against 09:00) fed newest-first. ⚠️ AND THE SOAK'S DRIFTING QUARTER WAS NOT A TIE. Six exactly equal 365.0 W quarters re-attributed zero times on the shipped tree - `>` is strict. What moved it was a real new maximum BELOW THE ROW'S OWN RESOLUTION: the row renders whole watts, so 365.0000001 W is a new peak to the database and the same 365 W to the reader. Left alone deliberately, and pinned so it is not re-diagnosed. test_tariff.py parts 11 and 12. 12 mutations, all red, listed on the PR; M2 - `banked_count()`'s sqlite3.Error arm returning 0 - was a SURVIVOR at -3 B on the first battery, because a handle that never opened short-circuits before any SQL runs and nothing reached the except arm. Closed with an open store whose table is dropped under it, with a precondition that the same call answered 4 first. main.py is NOT touched - TARIFF-11 holds its status rows. The row picks this up without editing because `recorded` is an attribute access and is now a property. The residual is stated in DECISIONS §3: `recorded` answers for now() while the peak follows `checks(when=...)`, and the shipped install has exactly one call site - `self.checks()` with no argument, main.py:4359 - where they are the same month, so the live page is correct and durable. `recorded_in(when)` is shipped and the row's move onto it is one token, for whoever holds main.py next; part 10 pins the present behaviour against a row count taken from `quarter_blocks` so the gap cannot be quietly forgotten. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BwRLw7eKYj2byVdwB6kbjU	2026-09-13 12:54:15 +02:00