SAFETY-90 review: count the start-up seconds like a gap

While the add-on is down the batteries are at 0 W (it sets 0 W when it
stops; the ESP32 watchdog after 30 s), so the import before its first
reading was the house, not the aim. Those seconds now count at
gap_w(limit, the import seen first), and after a restart the restored
reading's held 30 s is topped up the same way. Status row: "counted as
high use". Tests take the pre-start import as the house (batteries at
0 W) and add restarts of 10/60/150 s with a restored averager.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

goodwe_controller/DOCS.md

@@ -1760,8 +1760,9 @@ a 900 s billing quarter and commands nothing, and this stops the import.
 **After a gap it goes on (SAFETY-90).** The seconds the meter missed count at
 the higher of the peak limit and the import seen just before and just after
 the gap, with the batteries at 0 W. Seconds before the add-on's first reading
-count as on target, and the page says part of the period was not measured.
-DECISIONS/SAFETY-90-peak-guard-after-a-gap.md has the bound.
+count the same way, at the import seen first, and the page says part of the
+period was not measured. DECISIONS/SAFETY-90-peak-guard-after-a-gap.md has the
+bound.
 
 **It trips, where the freeze detector only notifies,** and the captures are why.
 On the healthy reference day (2026-08-23) it engages on **zero** of 95 quarters.