From 06cf0d33d6f49a3f0027d447fe86834fe7bcba1a Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Sun, 4 Oct 2026 21:55:50 -0500 Subject: [PATCH] docs(plans): lead decision 55, schema v3 accepted Co-Authored-By: Claude Opus 5.5 --- docs/SESSIONS.md | 2 ++ docs/plans/2026-09-26_lead-decisions.md | 10 ++++++++++ 2 files changed, 12 insertions(+) diff --git a/docs/SESSIONS.md b/docs/SESSIONS.md index a52e0361..0bba391a 100644 --- a/docs/SESSIONS.md +++ b/docs/SESSIONS.md @@ -481,3 +481,5 @@ are never rewritten or removed; corrections are new entries. 2026-10-04T23:42:31Z | Sage (T3 Claude Code, thread 1ef1e4f8) | slice 1 addendum B | Darkwing's addendum B (14e747f5) committed as a record; lead decision 52 accepts B1-B3 (sync bot, no agent reopen, schema v3 at brief time) 2026-10-05T02:45:53Z | Sage (T3 Claude Code, thread 1ef1e4f8) | PRDY round 3, PRD 0.4 | lead decision 53 (1A 2A 3A 4A 5A 7B; question 6 unanswered, so the PRD stays a draft); PRD draft 0.4; row 5 note: Gate E rides the slice 1 WebUI step 2026-10-05T02:52:27Z | Sage (T3 Claude Code, thread 1ef1e4f8) | slice 1 brief | brief 43c48d7a; epic #1515, row issues #1516-#1524; queue rows 34-42 (revs 64-72), rows 34-37 briefed (revs 73-76); lead decision 54 +2026-10-04 | rocko | Slice 1 S2 (#1519), row 37 preparation | Read brief, data model/addenda A+B and v2 prototype; preparation packet pinned; implementation held for schema v3 and Sage start instruction; S4 not started. +2026-10-05T02:55:50Z | Sage (T3 Claude Code, thread 1ef1e4f8) | schema v3 | Darkwing's schema v3 (7ed83178) rerun matched on Node 26; lead decision 55 keeps the task.missing body trigger; Rocko told S2 can start diff --git a/docs/plans/2026-09-26_lead-decisions.md b/docs/plans/2026-09-26_lead-decisions.md index 532e9419..b86ff23d 100644 --- a/docs/plans/2026-09-26_lead-decisions.md +++ b/docs/plans/2026-09-26_lead-decisions.md @@ -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.