docs(records): row 25 approver fix, second Discord restart, SetSpark approver and docker network gaps

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/plans/2026-09-26_lead-decisions.md

@@ -181,3 +181,16 @@ which stay with him. Each item names who decided it and what happened.
     each round stays small. C ships inside A1. Gate F's code goes ahead on
     Filbert's verdict, without a separate look from Jason. The design calls
     are the lead's (item 12).
+16. **Row 25 approvals, second fix and restart.** Jason's live check found no
+    Approve button. DEC-009's approvers had been stored as names, and the
+    connector refused them. Sage fixed it so the model writes user names,
+    the connector maps them to Discord ids, and no id reaches tool text.
+    Rocko approved R3, and the fix is 20ea5a0b, pushed. Sage restarted the
+    connector at 21:30:21Z, the second restart today. It is a local dev
+    service, and Jason was waiting on the check. Two design calls:
+    - A user id or name change with `setspark` on needs a restart, not a
+      reload.
+    - Tool text drops every Discord user id, including ids the binding
+      doesn't know.
+    The SetSpark service accepting free-text approvers is reported to
+    Jason as a shared-signals gap. Mosaic doesn't change it.

docs/plans/DEFERRED.md

@@ -114,6 +114,20 @@ at every gate. Started 2026-09-12 during the control board MVP.
   of the runtime files. Until then the rule is that unreviewed Discord source
   stays uncommitted in the tree only as long as a review needs it.
   (2026-09-26, #1509)
+- **SetSpark service accepts any string as a decision approver.** Create
+  checks only that `required_approvers` are distinct non-empty strings, and
+  approval checks `discord:<author id>` against them. So a decision stored
+  with names (DEC-009) can never be approved, and nothing says so until
+  an approval is tried. Mosaic's connector now writes only `discord:<id>`
+  (20ea5a0b), but the service should refuse other shapes. This belongs to
+  shared-signals, not Mosaic. Reported to Jason. (2026-09-26, #1509)
+- **Index-export suite runs leave Docker networks behind.** Each export
+  directory becomes a compose project, and its `<dir>_default` network
+  stays after the run. On 2026-09-26 the host ran out of address pools. The
+  task and release suites then failed 31 and 3 tests with "all predefined
+  address pools have been fully subnetted". Sage removed its own five stale
+  networks. The dw-* ones are still there. Fix: the export recipe, or the
+  suites, removes the project network on exit. (2026-09-26)
 
 ## Queue