Completes the native SynCode 0.3 control plane, including runtime authority, persistent node sessions, capacity admission, projection, audit, and the production-tested unavailable-capacity recovery path.
Runtime gate: node session 18/18, Clippy clean, architecture check clean, dev and production canaries passed.
Completes the native SynCode 0.3 control plane, including runtime authority, persistent node sessions, capacity admission, projection, audit, and the production-tested unavailable-capacity recovery path.
Runtime gate: node session 18/18, Clippy clean, architecture check clean, dev and production canaries passed.
A workflow is as many plans as it has jobs, so it is as many runs. Until now
anything with a second job was refused outright and produced nothing at all.
Measured against the five SynCode repositories, at the level of the jobs a node
would actually be handed, both sides now decide the same work: five jobs for
the runner, four for the control plane, one each for meta and the forge, none
where none. The comparison reads those jobs off the queue rather than off the
compilation, so what is counted is what would have been offered.
What this does not yet do is order them. Every plan carries the `needs` its job
declared, and nothing reads them: the queue still offers whatever is at the
front. So this control plane must not be pointed at a forge until it does, or
it would start a job before what it waits for has finished.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Completes the native SynCode 0.3 control plane, including runtime authority, persistent node sessions, capacity admission, projection, audit, and the production-tested unavailable-capacity recovery path.
Runtime gate: node session 18/18, Clippy clean, architecture check clean, dev and production canaries passed.
feat: open a run for every job a workflow declaresto feat: Complete control plane 0.3Reviewed for the SynCode 0.3 release. Runtime, rollback, architecture, and release evidence are complete.