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

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-09-26 16:31:11 -05:00
parent 20ea5a0b64
commit c5db8c8819
4 changed files with 78 additions and 0 deletions
@@ -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