docs(plans): lead decision 55, schema v3 accepted

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-04 21:55:50 -05:00
parent 7ed831781b
commit 06cf0d33d6
2 changed files with 12 additions and 0 deletions
@@ -904,3 +904,13 @@ which stay with him. Each item names who decided it and what happened.
      is today, since slice 1 has no container to isolate it in.
    - No new root directory. The runbook goes in `docs/guides/`, and the
      bundled Vikunja option goes in `packages/tasks/deploy/vikunja/`.
+55. **Schema v3 accepted (2026-10-04).** Source: Darkwing, commit
+    7ed83178, `agents/darkwing/work/slice1-proto/schema-v3.sql` (sha256
+    084d0a07…). Sage's rerun on Node 26.8.1 matched the recorded output.
+    Row 37 (S2) builds from it.
+    - The extra trigger `events_task_missing_body` stays. It enforces the
+      `task.missing` body that addendum B section 5 already defined: the
+      task in `subject`, a reason of `moved`, `not-found` or `no-access`,
+      and the new project id when the reason is `moved`. The v2 schema
+      checks `credential.*` bodies the same way, and an event the reader
+      can't act on is worse than a refused write.