harden versioned event substrate

This commit is contained in:
kami
2026-07-26 20:19:18 +04:00
parent 6bf6445d40
commit 4e05e4df7b
3 changed files with 37 additions and 11 deletions
+2
View File
@@ -53,6 +53,8 @@ The latest pass now applies `AuthorizeEvent` to lifecycle and approval writes an
The lifecycle API contract pass now requires callers to provide explicit release evidence (`reason` or `handoff_ref`), a block `blocker`, and a completion `report_ref`. The server no longer creates generated placeholder completion artifacts or converts malformed/empty lifecycle bodies into defaults. Regression coverage validates that release, completion, and block events reject missing evidence.
Item 1 substrate hardening pass: newly appended events use schema envelope version 1; replay rejects unsupported versions and non-object payloads; and `TaskLeased` carries an `expected_version` guard that is checked before append. Legacy envelope events remain readable for tolerant replay.
Recommended order:
1. Add the orchestration coordinator: lease → worktree → harness session → bootstrap → lifecycle events.