Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.
JavaScript agentic-codingai-agentsai-governanceautonomous-agentsclaude-codeclicode-reviewcodexcoding-agentsdeveloper-toolsgit-hooksllmlocal-firstmulti-agentsoftware-factoryspec-driven-developmentverificationvibe-coding
Merge main into core/801
Corey Olsone7b87804ee67
diff --cc docs/formats.mdindex 6cc01dab,84f5c4f2..aefacdd1--- a/docs/formats.md+++ b/docs/formats.md@@@ -176,8 -176,8 +176,10 @@@ Engine 61 (`NATIVE_FLAKE_ENGINE`) addsEngine 62 (`HEALTH_CAP_ENGINE`; engine 61 is #887's) caps what one recorded health run shouts. A run sends at most ten notices one by one, resolved first; when it has more, one more notice to the coordinator says how many it held back, and every finding still records its own health event. An idle seat alone hears that it is idle. A recorded run at an older engine replays with its original notices.+ Engine 63 (`RECURRING_JOB_ENGINE`) records recurring jobs. `declareJob` is the coordinator's or the person's: it stores a job's name, its cadence (`10m`, `2h`, `1d`, `hourly` or `daily`) and its owner, and a later declaration replaces the cadence and owner but keeps the run history. `recordJobRun` is any joined seat's and stores the job's name. Both events carry `engine: 63`. `pullboard health` reports a job with no run within one and a half cadences as `JOB_MISSED`, once per episode. An older engine refuses both moves with `ENGINE_VERSION`, and a replay at an older engine ignores their events.++Engine 64 (`LOCAL_LANDING_ENGINE`) lets a landing batch reach the state `trunk`: merged onto the local trunk after its quick guards (the static checks and submit invariants), with each item's merged receipt recorded before anything is pushed. Only a board whose `pullboard.json` sets `landing: { "publish": "separate" }` lands this way; `pullboard publish` then runs the whole suite on the exact trunk head and pushes only a green head. A batch recorded at an older engine still needs `pushed` before its receipts.+The CLI declares its engine in every relay request's `X-Pullboard-Engine` header.A linked board requires at least engine 48 after issuing any agent token or machine credential, includingrevoked or expired ones; before engine 48 these minimums were 3 and 6. The minimum survives reopening the auth database;diff --cc src/machine.jsindex 280c341a,47d00f4c..c0fb3b3c--- a/src/machine.js+++ b/src/machine.js@@@ -12,7 -12,7 +12,8 @@@import { RIGOR_NOTICE_ENGINE } from './rigor-source.js';import { HEALTH_CAP_ENGINE } from './health-receipts.js';import { NATIVE_FLAKE_ENGINE } from './flake-engine.js';+ import { RECURRING_JOB_ENGINE } from './job-engine.js';+import { LOCAL_LANDING_ENGINE } from './land-engine.js';/** First writer for withdraw-and-remove milestone behavior; shipment remains engine 45. */export const WITHDRAW_MILESTONE_ENGINE = 51;