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
test(companion): exercise catalog and pin replay additions [A1,H16]
Corey Olson7f3ace13da07
diff --git a/docs/formats.md b/docs/formats.mdindex aa186f46..e4f648a6 100644--- a/docs/formats.md+++ b/docs/formats.md@@ -422,6 +422,7 @@ The `event` table is a SQLite schema object governed by `SCHEMA_VERSION`; its ap| `model` | agent | — || `moved` | coordinator | `path` || `add` | item creator | `lane`, `specIds`, `after`, `route` |+| `companion` | requesting agent | `item`, `lane`, `key` (event item id names the parent) || `edit` | editor | `brief`, `route`, `criterion`, `check`, `unfrozen`, optional `after`, optional `pendingRefreeze`, engine-19 `reason`, `barCorrection` || `escalate` | builder | `from`, `to`, `note`, `attempt` || `attempt` | reporting agent | `n`, `seconds`, `result` |@@ -672,3 +673,5 @@ not a native move, parent identity, configuration or authority record. Missing/dreplays activity. Reads freeze an event high-water mark before observing Git; subsequent eventsand messages remain pending. News has a separate cursor so an ordinary poll cannot consume afuture 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.diff --git a/test/api-catalog.test.js b/test/api-catalog.test.jsindex b8e338bd..a83d4412 100644--- a/test/api-catalog.test.js+++ b/test/api-catalog.test.js@@ -734,6 +734,9 @@ catalogCase('[A1] catalog commands keep their real repository exercises', asyncassert.equal((await json(source, source.repo, 'loop', ['declare', 'catalog-job', '--every', '10m', '--owner', 'coordinator'], 'declare')).job.every, '10m');assert.equal((await json(source, source.repo, 'loop', ['ran', 'catalog-job'], 'ran')).job.runs, 1);assert.equal((await json(source, source.repo, 'loop')).jobs[0].name, 'catalog-job');+ const companion = await json(source, source.repo, 'companion', [String(catalog.item_id), 'coordinator', 'Catalog companion', '--key', 'catalog']);+ assert.equal(companion.item.item_parent_id, catalog.item_id);+ assert.equal(companion.created, true);await json(source, source.repo, 'milestone', ['add', 'Catalog', '--items', String(catalog.item_id)], 'add');await json(source, source.repo, 'milestone', ['items', 'Catalog', '--remove', String(catalog.item_id)], 'items');await json(source, source.repo, 'milestone', ['items', 'Catalog', '--add', String(catalog.item_id)], 'items');diff --git a/test/move-registry-baseline.json b/test/move-registry-baseline.jsonindex 64427929..98920214 100644--- a/test/move-registry-baseline.json+++ b/test/move-registry-baseline.json@@ -62,7 +62,8 @@"recordJobRun","takeCoordinator","landingLeaseMove",- "recordPublishFinding"+ "recordPublishFinding",+ "requestCompanion"],"itemIdFirstArgument": ["signBar",@@ -137,6 +138,7 @@}],"actors": {+ "requestCompanion": [null, "first", null, null, null, null],"openHandoff": [null,"first",@@ -6391,6 +6393,11 @@}],"nextSteps": {+ "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","BAD_VERDICT_WITHDRAW": "use --withdraw-verdict with a note, or report a conflict separately","VERDICT_WITHDRAW_FORBIDDEN": "ask the accepting reviewer or coordinator to withdraw this verdict","VERDICT_WITHDRAW_STATE": "refresh the item; withdraw only a current acceptance before landing",