The night end and rise were anchored on the first daily maximum,
which can be the 00:00 tail of the previous evening: 2026-05-05 was
read NO_CHARGE despite a +0.079 V rise, 2026-09-30 showed a wrong
night end, and 2026-09-26 stayed unknown from 04:00 to 11:00 when
evaluated mid-day. The rise now starts from an earlier minimum and
the knee is tested on the daily minimum (min_v). VERMONT: 139 / 31 /
14 / 0.
Docs: sheet 02 page order, battery_state.py in the CLAUDE.md map,
phase C exception to "anomaly = None means UNKNOWN".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Analysis 02 MOVING_AVERAGE_7_DAYS_MIDNIGHT_UTC_DROP: same rule as
analysis 01 on the 00:00 UTC BusVoltage sample only, one point per
day. Shared computation in energy_check._ma_drop(); analysis 01
results unchanged on VERMONT.
- Common page: one panel per analysis (02 under 01), then the time
series (D-016); src/analyse_02.py launches that page.
- Analysis panel reduced to two curves on one volt axis: 7-day mean
and threshold; gap and reference moved to hover (D-015).
- Date tick labels under every subplot.
- Rule IDs spelled out: MA7D_DROP -> MOVING_AVERAGE_7_DAYS_DROP,
MA7D_MIDNIGHT_DROP -> MOVING_AVERAGE_7_DAYS_MIDNIGHT_UTC_DROP (D-017).
- Docs: analysis sheet 02, sheet 01, CLAUDE.md, README, decisions
D-015..D-017, analysis rule and nouvelle-analyse skill.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>