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
fix(core): keep every login available in member lists [E17]
Corey Olson1b2f878eec6f
diff --git a/docs/api.md b/docs/api.mdindex 7b6400a2..fbe0e4db 100644--- a/docs/api.md+++ b/docs/api.md@@ -334,7 +334,7 @@ With `"relay": { "outbox": true }` in the committed `pullboard.json` (off by def`relay on --all [--url <address>]` returns `{version, linked: [{project, root, board}], failed: [{project, root, reason}], paired, autoLink: true}`. Its status is nonzero when a project failed; successful links remain available. With no paired phone, the command prints one tappable pairing link and QR, then waits in the foreground up to ten minutes. Interruption or expiration leaves completed links intact and exits zero when no link failed. Every explicit invocation signs in afresh; no person session is retained on the Mac. Later project registrations publish one sealed phone-link proposal and keep working locally until its single approval tap. `doctor` and `resume` name the waiting project and its expiry; expiration requires an explicit fresh sign-in rather than silently asking again. `relay off` excludes that project from automatic linking; explicit `relay on` clears the exclusion.-`pullboard relay members <login> [<login> ...]` publishes the next signed member-list revision for the linked board; `pullboard relay members clear` publishes an empty list. It is a person-only command and requires this computer to be linked. The signed list must be prepared by a committed approver using an SSH key currently on that approver's GitHub account. The command returns `{version, board, revision, members}`. Committed `pullboard.json` approvers remain trusted independently of the list. For other logins, device-key handover accepts a member only when the signed list names the same board and repository, its signer is a committed approver, and GitHub still verifies that signer's SSH key. A relay login by itself does not grant membership.+`pullboard relay members set <login> [<login> ...]` publishes the next signed member-list revision for the linked board; `pullboard relay members clear` publishes an empty list. It is a person-only command and requires this computer to be linked. The signed list must be prepared by a committed approver using an SSH key currently on that approver's GitHub account. The command returns `{version, board, revision, members}`. Committed `pullboard.json` approvers remain trusted independently of the list. For other logins, device-key handover accepts a member only when the signed list names the same board and repository, its signer is a committed approver, and GitHub still verifies that signer's SSH key. A relay login by itself does not grant membership.The board module exports `readBoardMembers(board)` and `setBoardMembers(board, {agentId, document})`. The reader returns `null` before a list is stored, or its exact `{body: {v, board, repository, revision, members}, by, signature}` document. The setter stores the next revision through the coordinator actor and refuses a mismatched board, unsupported engine, or skipped revision; it accepts an exact repeat idempotently. These are board-store APIs. The relay command prepares and verifies the SSH-signed document before passing it to the ordered setter.diff --git a/src/commands/relay.js b/src/commands/relay.jsindex 4c37408c..fe0781ab 100644--- a/src/commands/relay.js+++ b/src/commands/relay.js@@ -55,14 +55,14 @@ export async function run(io, { first, second, rest, values }) {if (['on', 'join'].includes(first) && gitSyncLinked(io.cwd)) throw new Refused('GIT_SYNC_LINKED', 'this board already shares moves through Git; it cannot start a second move order', 'keep using pullboard sync for this board');if (values['new-browser'] && first !== 'pair') throw new Refused('USAGE', 'pullboard relay pair --new-browser');if (first === 'members') {- if (!second || second === 'clear' && rest.length || values.url || values.all || values.skip) throw new Refused('USAGE', 'pullboard relay members <login> [<login> ...], or pullboard relay members clear');+ if (!['set', 'clear'].includes(second) || (second === 'set' ? !rest.length : rest.length) || values.url || values.all || values.skip) throw new Refused('USAGE', 'pullboard relay members set <login> [<login> ...], or pullboard relay members clear');requirePersonChannel(io.personChannel);const ctx = context(io);const state = relayMachineContext(ctx.info.root);if (!state || state.environment) throw new Refused('RELAY_NOT_LINKED', 'link this person’s computer before publishing board members');await withBoard(ctx, async board => {const revision = (store.readBoardMembers(board)?.body.revision ?? 0) + 1;- const document = await prepareBoardMembers(ctx.info.root, state, second === 'clear' ? [] : [second, ...rest], { githubKeys, revision });+ const document = await prepareBoardMembers(ctx.info.root, state, second === 'clear' ? [] : rest, { githubKeys, revision });await ordered(ctx, board, 'setBoardMembers', [{ agentId: whoAmI(ctx, board).id, document }]);io.result?.({ board: state.board, revision, members: document.body.members });io.say(`Board member list revision ${revision}: ${document.body.members.length ? document.body.members.join(', ') : 'no additional members'}.`);diff --git a/src/help.js b/src/help.jsindex c1072381..7ad6f78a 100644--- a/src/help.js+++ b/src/help.js@@ -57,7 +57,7 @@ Set uppullboard relay [status|on|off|pair|join <code>] [--url <address>] link, inspect or unlink this board's sealed relayon signs in through GitHub; the address defaults to https://app.pullboard.devpair prints a one-use machine code; join stores it in another clone- pullboard relay members <login> [<login> ...] | clear publish an approver-signed membership list+ pullboard relay members set <login> [<login> ...] | clear publish an approver-signed membership listpullboard relay pair --new-browser sign in and pair one more browser; existing browsers stay pairedpullboard relay on --all [--url <address>] link every registered project after one sign-in; pair the phone oncekeep this command open until pairing finishes; later projects link on registrationdiff --git a/src/next-step-defaults.js b/src/next-step-defaults.jsindex a933f4a1..8db971d1 100644--- a/src/next-step-defaults.js+++ b/src/next-step-defaults.js@@ -218,7 +218,7 @@ export const DEFAULT_NEXT_STEPS = Object.freeze({"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_NOT_MEMBER": "ask a committed approver to publish the board member list with pullboard relay members <login>, then retry relay on",+ "RELAY_NOT_MEMBER": "ask a committed approver to publish the board member list with pullboard relay members set <login>, then retry relay on","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",diff --git a/src/templates.js b/src/templates.jsindex f92d263f..6b991b2e 100644--- a/src/templates.js+++ b/src/templates.js@@ -166,7 +166,7 @@ When the person asks for help with Pullboard, such as "Help me open my Pullboard**Opening their board.** Start \`pullboard view\` yourself; it opens the board on this computer and prints its link. On app.pullboard.dev the browser may ask to let the page reach apps on this device: tell the person to click Allow, so the page can read the board running here. If they clicked Block, walk them through turning it back on: click the icon at the left of the address bar, open Site settings for app.pullboard.dev, set the access to apps on this device to Allow, then reload the page.-**Sharing with the phone or another computer.** Have the person type \`pullboard relay on --all\` themselves in their own terminal: it signs in as them, so Pullboard refuses it from an agent. Tell them what they will see: a GitHub address and a code to enter there, one \`linked:\` line for each board, then a QR code. To sign in on the phone, the person scans that QR code, taps Sign in with GitHub and approves Pullboard; their boards then appear on the phone. For another computer, the person runs \`pullboard relay pair\` in a board here and types \`pullboard relay join <code>\` on the other computer. Then confirm the boards arrived: run \`pullboard relay\` in each board to see its link, and \`pullboard relay devices\` to see the paired phone. The person can authorize additional developers with \`pullboard relay members <login>\` from the main checkout, using a committed approver’s SSH key. \`pullboard relay members clear\` removes additional members; relay identity alone never admits a device.+**Sharing with the phone or another computer.** Have the person type \`pullboard relay on --all\` themselves in their own terminal: it signs in as them, so Pullboard refuses it from an agent. Tell them what they will see: a GitHub address and a code to enter there, one \`linked:\` line for each board, then a QR code. To sign in on the phone, the person scans that QR code, taps Sign in with GitHub and approves Pullboard; their boards then appear on the phone. For another computer, the person runs \`pullboard relay pair\` in a board here and types \`pullboard relay join <code>\` on the other computer. Then confirm the boards arrived: run \`pullboard relay\` in each board to see its link, and \`pullboard relay devices\` to see the paired phone. The person can authorize additional developers with \`pullboard relay members set <login>\` from the main checkout, using a committed approver’s SSH key. \`pullboard relay members clear\` removes additional members; relay identity alone never admits a device.${AGENTS_END}`;}diff --git a/test/move-registry-baseline.json b/test/move-registry-baseline.jsonindex 45224d31..35bf04f9 100644--- a/test/move-registry-baseline.json+++ b/test/move-registry-baseline.json@@ -6964,7 +6964,7 @@"EXCLUDED_INVENTORY": "restore at most 256 excluded boards and their active paired devices, then run pullboard relay on --all","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 <login>, then retry relay on"+ "RELAY_NOT_MEMBER": "ask a committed approver to publish the board member list with pullboard relay members set <login>, then retry relay on"},"replay": {"initial": {diff --git a/test/team.test.js b/test/team.test.jsindex 16f5905e..c7ac8f7c 100644--- a/test/team.test.js+++ b/test/team.test.js@@ -749,7 +749,7 @@ test('a clone of a linked repo joins its board; a member device hands over the kassert.equal(kept.document?.error?.code, 'RELAY_JOIN_NOT_EMPTY', `a clone with work of its own is not joined over it: ${JSON.stringify(kept.document?.error ?? null)}`);assert.equal(box.auth.linkedBoards().length, 1);- const members = await box.cli('relay', 'members', 'bob');+ const members = await box.cli('relay', 'members', 'set', 'bob');assert.equal(members.code, 0, `alice publishes a real signed member list: ${members.stderr}`);assert.deepEqual(members.document.members, ['bob']);