MAINT-21: comments only - trim restated notes, add DECISIONS pointers

No code change: tools/maint21_same_ast.py and tools/maint20_same_code.py HEAD~
both print OK, and the -OO code objects are the same.

- Trims 56 comment and docstring lines (2088 -> 2032) in app/main.py and the
  new files that only restated their MAIN-orchestration.md bullet, each cut to
  its first sentence and a pointer. What the cut comments said and the bullet
  did not is now in the bullet: why a SAFETY-02 latch is restored, why the
  SAFETY-30 site check is not armed at one inverter, the SAFETY-18 re-derive,
  the MAINT-05 one-config rule, the OPT-09 sizing rules, the "no plan" row,
  the 5 400 s age bound, and the guard being the only latch repair.
- Adds the missing DECISIONS pointers on the SMA-10, SAFETY-137 and SMA-2
  comments (FALLBACK_BUDGET_S, write_setpoint, _await_inflight,
  _release_last, the retry wait, the failed-release branch, release_zero_sent,
  the in-flight write, the stop_event hand-back, the SMA-2 read and driver).
- DECISIONS/SAFETY-32: the stale `main.py:932-936` now names
  Controller.pack_floor_soc.
- main.py's docstring and import block say where the Controller's parts are.

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

goodwe_controller/app/ctl_tasks.py

@@ -21,13 +21,8 @@ _LOG = logging.getLogger("goodwe")
 class TasksMixin:
     def _grade_store_migration(self, store) -> None:
         """DEV-02. Did SAFETY-02's latch actually survive the key rename?
-        Graded, not performed: a latch that silently fails to move is a
-        DISARMED SAFETY GUARD on an install that believes it is protected. The
-        pre-DEV-02 flat value is compared with what the roster came up with; a
-        disagreement re-arms the latch by hand (the fail-safe direction is ON).
-        It runs on EVERY start, not only the migrating one: gating on `rep.ran`
-        swallowed store.py's rule-2 round trip (upgrade, downgrade with a trip
-        in the window, upgrade; performed on this site 2026-09-02).
+        Graded on EVERY start: a latch that silently fails to move is a
+        disarmed safety guard, so a disagreement re-arms it by hand.
         DECISIONS/MAIN-orchestration.md."""
         rep = self.store_migration
         if rep.ran and not rep.ok:
@@ -38,16 +33,10 @@ class TasksMixin:
         legacy_tripped = bool(data.get("sign_tripped", False))
         if not legacy_tripped or not self.inverters:
             return
-        # The question is "is any namespaced latch set THAT A MACHINE READS"
-        # (SAFETY-44), asked of the STORE's keys, not the roster's objects:
-        # re-arming A off a flat key that B's trip mirrored would latch a
-        # healthy inverter on every restart. Three cases: on the roster, stop;
-        # off-roster named `UNIT_A` (the broken migration's fingerprint),
-        # repair onto `inverters[0]`; off-roster, other name: stop unless a
-        # stranded `UNIT_A` latch is present. This guard is the ONLY repair for
-        # sites upgraded before the fix. Residual: a first unit really named
-        # `inverter-a`, latched and removed, is re-armed on `inverters[0]`
-        # (conservative). DECISIONS/MAIN-orchestration.md.
+        # Is any namespaced latch set THAT A MACHINE READS (SAFETY-44)? Asked
+        # of the STORE's keys, not the roster's objects. On the roster: stop;
+        # off-roster `UNIT_A`: repair onto `inverters[0]`; any other
+        # off-roster name: stop. DECISIONS/MAIN-orchestration.md.
         on_roster = {inv.name for inv in self.inverters}
         stranded, on_roster_latched, other_off_roster = [], False, False
         for k, v in data.items():
@@ -193,7 +182,8 @@ class TasksMixin:
             self.log_event("REFUSED: " + problems[0],
                            hint=messages.hint("refused"))
             # Signal and return WITHOUT entering the loop: amain() runs the
-            # wind-down (0 W, or a hand-back: SMA-10) and exits with code 78.
+            # wind-down (0 W, or a hand-back: SMA-10, see
+            # DECISIONS/SMA-10-two-idle-states.md) and exits with code 78.
             self.stop_event.set()
             return