Batch-integrate finished runs — cyberine land
cyberine land collapses the whole landing leg (wait -> digest -> apply+commit per run -> one final
typecheck for the batch) into a single command — the integration step of the two-turn dogfood
protocol:
cyberine land <runId1> <runId2> ... # land each run in order, commit per run, ONE final npm run typecheck
cyberine land <runId1> <runId2> --dry-run # digests + apply checks only, no commitsPer run it waits for a terminal state, prints the compact digest, verifies the winning diff
applies cleanly, applies + commits it, then runs ONE npm run typecheck for the whole batch
(catches cross-run interactions per-run gates cannot see) and prints a summary table (runId,
diffstat, commit, RISK flags). Stops on the first apply/typecheck failure and reports landed vs
not landed. RunId prefixes resolve like cyberine apply.
Recurring scheduled dispatches — cyberine cron
Cyberine can re-dispatch a task on a schedule. Jobs are persisted in <CYBERINEHOME>/cron.json (so they survive restarts) and are dispatched as detached background runs (cyberine run --bg) when a...
See what's runnable + dispatch by id — cyberine next
cyberine next derives the runnable / blocked / waiting sets from the project task manifest (.claude/TASKS.md or .local/tasks/ACTIVE.md) — the same deps + blocker logic the global oc-tasks tool's...