kami/orchestra
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

enforce lifecycle evidence contracts

Browse Source
This commit is contained in:
kami
2026-07-26 20:17:03 +04:00
parent b2b24cbe09
commit 6bf6445d40
3 changed files with 31 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
progress.md
+2
View File
@@ -51,6 +51,8 @@ The first pass closed the store/API defects (lifecycle defaults, CAS content ver
The latest pass now applies `AuthorizeEvent` to lifecycle and approval writes and adds `/readyz` with router/provider configuration checks. Readiness is configuration-level only; it does not yet probe herdr/provider health.
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.
Recommended order:
1. Add the orchestration coordinator: lease → worktree → harness session → bootstrap → lifecycle events.