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.