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.

fix(merge): a companion request is a [C7,H16,P4,B2,B12,H2,A5,A1]

Corey Olson327cd49e1e49
diff --cc docs/formats.md
index 7c4dd657,a5d7b8a9..931e0fe9
--- a/docs/formats.md
+++ b/docs/formats.md
@@@ -115,7 -115,7 +115,7 @@@ The version table is generated from th
| `row grammar` | `1` | `SPEC_GRAMMAR_VERSION` in `src/spec.js`; optional `<!-- pullboard-grammar N -->` line in either file (absence means the current grammar) | Both files share the version. A declared version must match; an incompatible grammar change requires a coordinated version bump and compatible files. No automatic conversion occurs. |
| `board schema` | `3` | `SCHEMA_VERSION` in `src/board.js`, persisted as `PRAGMA user_version` | On a write open of a board whose version is behind: create missing tables and indexes (version 3 adds the hot-path indexes), add missing columns in place with declared defaults, restore missing or changed triggers, and remove stale machine triggers without replacing rows. Read opens never migrate; a board at the current version whose shape differs is reported once on stderr and left as it is. |
| `event log` | `1` | `EVENT_LOG_VERSION` in `src/board.js`, persisted in `board_meta` as `event_log_version` | Older event-log versions upgrade in place; newer versions are refused with `EVENT_LOG_VERSION`. Preserve event rows when the board schema changes. |
- | `move engine` | `122` | `ENGINE_VERSION` in `src/machine.js`, carried as `engine` in every sealed executable move | Bump when a move's meaning changes, independently of the event log and sealed envelope. A newer engine is refused with `ENGINE_VERSION`, naming both versions and asking you to upgrade Pullboard. |
-| `move engine` | `121` | `ENGINE_VERSION` in `src/machine.js`, carried as `engine` in every sealed executable move | Bump when a move's meaning changes, independently of the event log and sealed envelope. A newer engine is refused with `ENGINE_VERSION`, naming both versions and asking you to upgrade Pullboard. |
++| `move engine` | `123` | `ENGINE_VERSION` in `src/machine.js`, carried as `engine` in every sealed executable move | Bump when a move's meaning changes, independently of the event log and sealed envelope. A newer engine is refused with `ENGINE_VERSION`, naming both versions and asking you to upgrade Pullboard. |
<!-- format-versions:end -->
A builder never picks an engine number (#1101). An item that adds a board move adds its own `src/<name>-engine.js` leaf as `export const NAME_ENGINE = unassignedEngine();` (importing `unassignedEngine` from `./engine-next.js`); on its branch the leaf reads as one above the highest landed engine. The landing merge writes the next number into the leaf, in landing order, inside that item's merge commit, and sets the `move engine` row above to the highest landed number. A landed number never changes, so recorded moves replay as they were written. Moves are recorded under landed numbers only: code with an unnumbered engine is for its branch's own tests, and a move it records on a real board before landing may later read under another item's number, so the item lands before its moves are used.
diff --cc src/companion-engine.js
index 00000000,b3e4703f..83e5ee11
mode 000000,100644..100644
--- a/src/companion-engine.js
+++ b/src/companion-engine.js
@@@ -1,0 -1,3 +1,2 @@@
+ /** Atomic cross-lane companion requests receive their replay number at landing [B2,B12,H16]. */
-import { unassignedEngine } from './engine-next.js';
-export const COMPANION_ENGINE = unassignedEngine();
++export const COMPANION_ENGINE = 123;
diff --cc src/next-step-defaults.js
index ed7f080b,3403090b..8806fab4
--- a/src/next-step-defaults.js
+++ b/src/next-step-defaults.js
@@@ -1,8 -1,10 +1,13 @@@
/** General CLI recovery text; operation-owned codes live in src/moves/ [P4,C7]. */
export const DEFAULT_NEXT_STEPS = Object.freeze({
+ "DECISIONS_NOT_AVAILABLE": "read each board's state from the local API, which carries its own person decisions",
+ "PROJECT_REPO_AMBIGUOUS": "run pullboard decisions --as person and answer with the repo name it prints before the #",
+ "PROJECT_REPO_UNKNOWN": "run pullboard decisions --as person to see the repos of this project, then answer repo#id",
+ "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",
"BOARD_REFERENCE": "use an immutable board ID or one exact qualified name from the authorized project inventory",
"BOARD_LINK_FORMAT": "use the exact bounded version 1 board-link, approval, announcement or sealed envelope contract",
"BOARD_LINK_AUTH": "configure each board’s established signer authority and the per-link sealing capability; never use an unsigned or full-board-key fallback",