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

validate and select configured harness adapters

Browse Source
This commit is contained in:
kami
2026-07-26 20:25:17 +04:00
parent 4e05e4df7b
commit 98725c28c5
3 changed files with 22 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
progress.md
+2
View File
@@ -55,6 +55,8 @@ The lifecycle API contract pass now requires callers to provide explicit release
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.
Harness registration now uses configured `harness` and `protocol` fields, pings each configured herdr before exposing it to orchestration, selects Claude/Codex/opencode adapters accordingly, and skips unavailable or unsupported deployments at startup. This is an initial discovery/health slice; active-session discovery and ongoing heartbeats remain open.
Recommended order:
1. Add the orchestration coordinator: lease → worktree → harness session → bootstrap → lifecycle events.