docs(plans): slice 1 prototype v2 records; lead decision 50

Darkwing's schema-v2 adds task_snapshots, decisions.blocking and a
closed events.kind list. Sage reran proto-v2 on Node 26 with matching
output. Decision 50 accepts the five choices beyond addendum A.

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

docs/SESSIONS.md

@@ -473,3 +473,4 @@ are never rewritten or removed; corrections are new entries.
 2026-10-04T19:26:50Z | Sage (T3 Claude Code, thread 1ef1e4f8) | meta-harness survey received | Filbert's survey (05f83807) committed as a record; lead decision 47 rules on its section 8; two DEFERRED items (host-seat --approve, worker provider-key exposure)
 2026-10-04T19:48:15Z | Sage (T3 Claude Code, thread 1ef1e4f8) | PRDY round 2, PRD 0.2 | lead decision 48; PRD draft 0.2 with requirement ids; Researcher's Vikunja and Pocket ID report (fcfc970f) committed as a record (Researcher wrote no SESSIONS line, per its limits)
 2026-10-04T19:56:14Z | Sage (T3 Claude Code, thread 1ef1e4f8) | slice 1 addendum A | Darkwing's addendum (0b36acb0) committed as a record; lead decision 49; PRD draft 0.3; assigned Researcher Vikunja probes P1-P7 on a scratch container and Darkwing the task_snapshots prototype extension
+2026-10-04T19:59:24Z | Sage (T3 Claude Code, thread 1ef1e4f8) | slice 1 prototype v2 | Darkwing's schema-v2, proto-v2 and outputs committed as records after a Sage rerun on Node 26; lead decision 50 accepts the five choices beyond addendum A; Researcher probes P1-P7 still running

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

@@ -803,3 +803,24 @@ which stay with him. Each item names who decided it and what happened.
       in the slice 1 brief (REQ-CLI-2).
     - PRD wording for REQ-VAR-2 and REQ-TASK-1 adopted in draft 0.3, with
       REQ-TASK-2 updated for A2.
+50. **Sage's rulings on the slice 1 prototype v2 (2026-10-04).** Source:
+    Darkwing (CTO), `agents/darkwing/work/slice1-proto/proto-v2-notes.md`
+    (sha256 90ce5645…), `schema-v2.sql` (ffb7cf90…) and `proto-v2.mjs`
+    (d428da74…). Sage reran `proto-v2.mjs` on Node 26.8.1 and got the
+    same output as Darkwing's Node 26 run, apart from version lines.
+    `schema-v2.sql` replaces `schema.sql` as the design the broker
+    starts from.
+    - A blocking decision must cite a task (trigger): accepted. Slice 1
+      has no blocking work outside a task. If one turns up, the broker
+      files a task first.
+    - `launch.revoked` and `launch.restored` carry no role and no run:
+      accepted. An empty role is not proof of a human. The broker must
+      write these only from the CLI path that runs outside any agent run
+      (REQ-DEC-3). The slice 1 brief states that.
+    - `credential.*` events name a service and a role instance: accepted.
+    - The open-time digest covers every schema object: accepted. This
+      check notices tampering, it doesn't prevent it, the same limit as
+      the triggers.
+    - The three views: accepted as demonstrations. Counting a person's
+      edit in the same second as a broker write as external is the
+      cautious side, and stays.