Skip to content

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.

chore(merge): carry main into the companion item [B1]

Corey Olson49fabff779fd
diff --cc docs/formats.md
index 5e09a7e5,96115db6..a5d7b8a9
--- a/docs/formats.md
+++ b/docs/formats.md
@@@ -705,7 -705,9 +706,11 @@@ replays activity. Reads freeze an even
and messages remain pending. News has a separate cursor so an ordinary poll cannot consume a
future session-start digest.
+Companion requests use the `requestCompanion` move and the unassigned `COMPANION_ENGINE` boundary allocated at landing. The authenticated first argument names `agentId`, `parentId`, target `lane` and stable `key`. A `board_meta` key `companion:` plus SHA-256 of JSON `[parentId,lane,key]` binds that identity to its child. The immediate transaction creates the ordinary item, records its check baseline and bar, appends the companion event, and stores the binding. A retry returns the existing child without changing its contents or claim. Ordinary `addItem` parent-lane validation remains unchanged.
++
+ ### Signed board membership
+
+ `setBoardMembers` records an exact next revision in `board_meta.board_members` and a `board_members` event. Its signed document is `{body:{v:1,board,repository,revision,members},by,signature}`; the SSH namespace is `pullboard-board-members` and the bytes are the JSON array `["pullboard-board-members",body,by]`. Repeating the identical document is idempotent. A new empty list removes all additional members. Native ordered transport and checkpoints seal this document with the board key. A key handover independently checks the approving login against committed `pullboard.json` approvers and its SSH signature against GitHub; stored or relay-provided identity flags alone never authorize a handover. Every requester also proves ownership of its own device key. The current native revision is authoritative; an old signature cannot roll back that state.
## Seat addresses
A seat address is `pullboard:<board-id>:<percent-encoded-seat-id>`, where `board-id` is the board’s existing 32-character hexadecimal `board_id` and the seat component is the canonical JavaScript `encodeURIComponent` encoding of its registered agent id. It is independent of machine and checkout path. `whoami` and `agents` expose it; `shout` resolves it only within the current board and records the existing shout event with the exact recipient agent id. It is a destination, never a grant. Existing relay board credentials and authenticated sender attribution remain required on linked boards. No new stored event or file format is introduced.
diff --cc src/board.js
index 98426bac,148e0b5d..4627fb36
--- a/src/board.js
+++ b/src/board.js
@@@ -1,5 -1,4 +1,6 @@@
+import { companionPlan } from './companion.js';
+import { applyCompanionRequest } from './companion.js';
+ export { readBoardMembers, setBoardMembers } from './board-members.js';
import { heartbeatSeat } from './seat-presence.js';
import * as itemDecisions from './item-decision-queue.js';
import * as activityDeliveryStore from './activity-delivery-store.js';
diff --cc test/move-registry-baseline.json
index 2473402a,1e81beea..5ce341ee
--- a/test/move-registry-baseline.json
+++ b/test/move-registry-baseline.json
@@@ -67,7 -67,7 +67,8 @@@
"recordActivityDelivery",
"decideSpecRevisions",
"recordRowVerification",
- "requestCompanion"
++ "requestCompanion",
+ "setBoardMembers"
],
"itemIdFirstArgument": [
"signBar",
@@@ -669,13 -669,13 +670,21 @@@
null,
null
],
+ "setBoardMembers": [
+ null,
+ "first",
+ null,
+ null,
+ null,
+ null
++ ],
+ "requestCompanion": [
+ null,
+ "first",
+ null,
+ null,
+ null,
+ null
]
},
"floorCases": [
@@@ -7042,11 -7042,20 +7051,23 @@@
"ROW_VERIFY_PROVENANCE": "draft the row through pullboard spec draft and join normally before verifying it",
"ROW_VERIFY_PENDING": "ask the coordinator to run pullboard spec apply before recording a verifier verdict",
"ROW_VERIFY_SELF": "ask an outside-parent verifier to run pullboard spec verify",
+ "BOARD_MEMBERS_INVALID": "ask a committed approver to publish a complete signed board member list",
+ "BOARD_MEMBERS_REVISION": "read the current member revision, then sign a new list",
+ "RELAY_NOT_MEMBER": "ask a committed approver to publish the board member list with pullboard relay members set <login>, then retry relay on",
+ "BOARD_REPLACE": "run pullboard relay on again; a relink replaces only the repository's active board",
+ "BOARD_REPO_LINKED": "pull pullboard.json from main, which names the repository's board, then run pullboard relay on again to join it",
+ "GITHUB_UNAVAILABLE": "run any pullboard command again once GitHub answers; the new device keeps waiting",
+ "RELAY_JOIN_NOT_EMPTY": "keep this board, then run pullboard init and pullboard relay on in a fresh clone to join the team board",
+ "RELAY_KEY_VOUCH": "add the SSH key that signed this device to your GitHub account with gh ssh-key add, then run pullboard relay on again",
+ "RELAY_KEY_WAIT_EXPIRED": "run pullboard relay on again while a linked computer of this repository is online",
+ "RELAY_SSH_KEY": "make an SSH key with ssh-keygen -t ed25519, add it to GitHub with gh ssh-key add, then run pullboard relay on again",
+ "RELAY_SSH_KEYGEN": "install OpenSSH, then run pullboard relay on again",
+ "RELAY_SSH_SIGN": "load the key with ssh-add, or set PULLBOARD_SSH_KEY to a key on your GitHub account, then run pullboard relay on again",
- "BAD_DECISION_OPTIONS": "ask an item decision with --decision --item <id> --options '[\"first\",\"second\"]'",
- "NOT_YOUR_ITEM_DECISION": "ask on an item you build or review, or ask the coordinator for a cross-item decision"
+ "COMPANION_PARENT": "name the parent item: pullboard companion <parent> <lane> \"<title>\" --key <key>",
+ "COMPANION_KEY": "supply a stable --key and reuse it for this same parent and target lane",
+ "COMPANION_LANE": "choose a different target lane; ordinary same-lane children use pullboard add --parent",
+ "COMPANION_CONTENT": "supply title, criterion and brief text and existing spec ids for the companion",
+ "COMPANION_RECORD": "restore a consistent board export so the companion request index matches its child"
},
"replay": {
"initial": {