Answer A-129 and A-130: kept-points says the unrestored asides; the recovery settings' names

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent 29692693fa
commit 53f119fb48
1 changed files with 4 additions and 0 deletions
@@ -502,3 +502,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-128** (A-116; principle 7) A `reads` in seat form `seat:<seat>.<state>` is parsed by mesh-sdk's state reader as
  its own kind, kept apart from a module's read; the validator checks the seat declares the state, and the holder is
  resolved where it is read, by A-126's helper.
+- **A-129** (§657; principle 4) The seat's `kept-points` answer gains `unrestored`, the asides whose record ended at
+  `removed`, read from the engine; the tool `recovery_kept_points` shows it, and the health check reads the same.
+- **A-130** (A-124, §557; principle 7) The events `set-aside` and `aside-discarded` carry `names` as `Aside` does; the
+  recovery module's two bounds are the settings `dump-wait-minutes` (default 60) and `point-keep-days`.