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 branch 'main' into core/221
Corey Olson59f49ceba0be
diff --cc docs/formats.mdindex 8b7855c1,545a1e5f..5a2c5016--- a/docs/formats.md+++ b/docs/formats.md@@@ -530,17 -530,4 +530,19 @@@ Engine 68 retains the existing validateThe engine-68 `recordSpecApprovalBaseline` move carries `{agentId, baseline: {version: 1, file, anchor, rows: [{id, text, source}]}}`. `anchor` is the current commit or `null` before the first commit; exact source rows also cover uncommitted initial requirements. Only the authenticated coordinator may establish the snapshot; a person uses the main checkout’s coordinator path. Lane commands never seed or replace it. The first snapshot is indexed under `board_meta.spec_approval_baseline` with a `spec_approval_baseline` event. Replay writes metadata only, never checkout files. Sender attribution is authenticated normally, older engines refuse the new move, and later bootstrap attempts cannot replace or expand the original snapshot. No local sidecar establishes shared approval authority. The metadata snapshot must agree with its single original coordinator event; a partial restore with either half missing or changed is invalid. A malformed stored marker remains in place with an invalid-baseline diagnostic; it is not treated as an absent migration baseline or reseeded by later commands. Board imports remain trusted recovery operations; agreement of these records is a consistency check, not cryptographic authentication of an imported history.+## Recorded board line settings++`pullboard settings line --json` reads six board-owned controller inputs. All default to `false` (off), independently of machine `gate.queue` or `pullboard.json`. `pullboard settings line <name> <on|off|number> --reason "why" --window '{"windowMinutes":60,"activeReviewers":2}'` records a coordinator-owned `setLineSetting` move. The window is a nonempty object of named finite nonnegative numbers, with `null` retaining an unknown measurement. A nonempty reason is required.++| Setting | Enabled values | Off |+| --- | --- | --- |+| `reviewsFirst` | `true` (`on`) | `false` |+| `wipPerReviewer` | 1.5 through 3 | `false` |+| `barReady` | `true` (`on`) | `false` |+| `takeoverMinutes` | whole minutes 15 through 60 | `false` |+| `landingBatchSize` | whole numbers 1 through 8 | `false` |+| `landingCadenceMinutes` | whole minutes 5 through 30 | `false` |++These are recorded inputs only (#1096); this step does not enforce queue, takeover or landing behavior. The move carries `{agentId,key,value,reason,window}`; its native `line_setting` event carries `{key,value,reason,window}` with the board's actor and time outside that detail. Latest values live under `board_meta` keys `line_setting:<name>`, and ordered engine replay updates them and appends the same evidence. The unassigned `LINE_SETTINGS_ENGINE` leaf receives its permanent number at landing. Older engine records cannot request this new operation. Range, unknown-key, missing-reason and invalid-window refusals have named codes. The existing settings API reports each input as `scope: "board"`, key `line.<name>`, with off as its default and the board SQLite file as its source; it does not expose reason text or evidence payloads through that inventory.+++ Engine 93 adds item-addressed shouts. A shout move's optional `item` names an existing item; its event belongs to that item and includes the message text. Its canonical `shout_to` is `item:<id>`, read by the item's current builder and reviewer and the coordinator. Inbox, resume and seat watch use the same audience; an explicit seat or lane destination with `--item` still uses the item's audience. An item decision is answerable by its current participants or coordinator; replies stay in its thread and audience. The coordinator can still pass it to the person through the existing decision flow. A registered seat's shout to `all` is accepted and stored at reserved address `coordinator+person`, read only by coordination audiences. The plus sign cannot occur in valid lane names or their derived seat ids. Coordinator and person broadcasts retain `all` and reach everyone; recorded older-engine `all` rows retain their original global meaning without a retrospective sender filter. Main-checkout watch remains the person's board-wide observer. A joined seat's default watch filters shouts to its own address, lane, items and `all`, while ordinary lifecycle events remain visible.diff --cc src/board.jsindex 11780ec4,5a8f1c13..337a2806--- a/src/board.js+++ b/src/board.js@@@ -1,4 -1,12 +1,14 @@@+export { lineSettings, setLineSetting } from './line-settings.js';+++ import { ITEM_SHOUT_ENGINE } from './item-shout-engine.js';+ import {+ COORDINATION_SHOUT,+ itemShoutTarget,+ itemShoutReader,+ shoutItemId,+ UNREAD_SHOUT_SQL,+ unreadShoutBindings,+ } from './shout-audience.js';import { recordVerdict } from './verdict-assurance.js';import { logEvent } from './board-event-log.js';export { logEvent };diff --cc src/help.jsindex 139ed415,5b099785..60ff1687--- a/src/help.js+++ b/src/help.js@@@ -24,8 -24,6 +24,9 @@@ Set upullboard takeover rebind this checkout when the same agent starts a new sessionin a linked main checkout it also takes the board's coordinator herepullboard resources local resource holders and their FIFO queues- pullboard settings line [<name> <on|off|number> --reason "why" --window <json>] read or record board controller inputs; all off by default, no queue enforcement++ pullboard settings line [<name> <value> --reason "why" --window <json>] read or record board controller inputs; all off by default, no queue enforcement++ value is on, off, or a number within the setting range+ names: reviewsFirst, wipPerReviewer (1.5-3), barReady, takeoverMinutes (15-60), landingBatchSize (1-8), landingCadenceMinutes (5-30)pullboard settings [gateSlots <n> | browserSlots <n>] view or set machine capacity (gate default 2; browser default 1)browser-free check slots are opt-in: gate.browserFreeChecks in ~/.pullboard/settings.json (default false)a test file takes a browser slot only if it launches Chrome: gate.browserByLaunch (default false)