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 commit 'dd3d651b61febe103721ebf33047ff7eb302d71d' into core/814-haiku-b
Corey Olsonade51098d640
diff --cc docs/api.mdindex ee0ba4bb,e8383c63..58583429--- a/docs/api.md+++ b/docs/api.md@@@ -34,10 -34,10 +34,12 @@@ Freshness never rewrites the stored ACCFor a stale acceptance, merge current main into the submitted work and commit a clean review HEAD. Another agent runs `pullboard verify <id> accept --note "what was re-reviewed"`; its frozen check runs at that combined HEAD, and a new verdict appends to the history while retaining the original submitted commit. A main move during the check refuses `VERDICT_TRUNK_MOVED` and requires another review. `resume` keeps stale acceptances out of its merge list. `land` excludes stale items (and reports their file and commit); when none remain ready, it refuses `STALE_VERDICT`. Nothing in this observation changes the approved criterion or grants person authority.+ A submit that edits a test file, `pullboard.json`, a githook or a file a gate command names, and that already existed at the claim, is refused with `INFRA_NOTE_REQUIRED` until it carries `--infra "<why>"`. The refusal names the files. The note and those files are recorded on the item's `submit` event as `infra: {note, files}`, and `pullboard show` prints them for the reviewer as `infra note:`. A new test file needs no note.+`pullboard stats [--since <date>] --json` returns `{version: 1, stats: {...}}` from the append-only event log. `submissions` and `rejections` count moves, including repeated attempts; `rejectionShare` is rejections divided by submissions (zero when the window has no submissions). `merged` counts distinct items with a merge move; `mergedWithoutAccept` counts those whose merge lacks an earlier acceptance of the latest submitted commit. That audit uses earlier history even when the acceptance falls before the selected window. Current item and verdict rows do not replace event evidence.+`gateWaits`, beside `stats`, lists, for each kind of gated run in the last day (`check`, `review`, `doctrine`, `gate`, `landing`), its `runs`, `medianWaitMs`, `slowestWaitMs` and `medianRunMs`, read from the board's gate receipts; text `stats` prints them under `gate waits, last day:`. A gate receipt is written for every run that takes a gate slot. Its fields are `waitMs` (queued for a slot), `admissionMs` (deciding and queueing, then handing over), `setupMs`, `runMs` and `evidenceMs` (reading the result and writing its record), and `slot: {kind, reason}`, where `kind` is `ordinary`, `browser`, `short`, `runner` or `inherited`. A timing profile carries it as `receipt`, `check --json` returns it as `receipt`, and the timing lines print it as `phases: ...; slot: <kind> (<reason>)`. A doctrine hold at submit prints its own `doctrine hold phases:` line.+`stats.bars` counts bar corrections, keyed by agent: `{corrections, barRejects, buildRejects}`. A correction is an `edit --criterion` or `--check` on an item that was ever claimed. It must carry `--reason "what the old bar got wrong"` (HTTP `args.reason`); without one it is refused with `BAR_REASON`. A correction that follows the item's newest, unexplained reject marks that reject as caused by the bar, counted to the correcting agent; every other reject counts to the build, under the agent who added the item. Text `stats` prints one `bars:` line per agent, and text `show` prints each correction with its reason.`stats.flow` adds the flow through the board:diff --cc src/next-steps.jsindex 0dc58ab7,85f09d37..71bad03b--- a/src/next-steps.js+++ b/src/next-steps.js@@@ -277,12 -269,7 +277,13 @@@ export const NEXT_STEPS = Object.freezeGATE_SLOT_LEASE_REQUIRED: 'start the child test process with the live gate lease',GATE_SLOT_MARKER_INVALID: 'restart the child with gateSlotEnvironment(lease)',GATE_SLOT_TOKEN_REQUIRED: 'restart the child with gateSlotEnvironment(lease)',+ NO_SNAPSHOT: 'run pullboard relay from the linked computer to publish its saved snapshot, then refresh the phone',+ RELAY_API_VERSION: 'upgrade Pullboard on every joined computer and the configured relay before retrying; keep the local board and pending data',+ RELAY_CLOCK: 'ask the relay operator to restore a valid service clock, then retry the saved upload or read',+ RELAY_CLOSED: 'restart the relay service before retrying the saved operation',+ RELAY_CONFIG: 'ask the relay operator to repair the named service setting and restart; retain the local board and pending upload',+ RELAY_PAGE_CACHE: 'close other local Pullboard commands, then restore the private relay-pages cache permissions or remove only that device cache and retry; keep the board, relay link and key',+ INFRA_NOTE_REQUIRED: 'run pullboard submit <id> --infra "<why>" with the reason the edit to an existing test or gate file is needed',SHORT_SLOT_FULL_SUITE: 'run the whole suite outside the short check, where it queues for an ordinary gate slot; short slots are only for runs that name their test files',GIT_GRAFTS: 'ask the coordinator to remove the git graft file: pullboard shout coordinator "please remove .git/info/grafts"',HEAD_NOT_NEW: 'commit the rework, then pullboard submit <id>',