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): retain lane leads and runner deadline recovery [B21,H16]

Corey Olsonb425f4eba042
diff --cc test/move-registry-baseline.json
index cd30457f,449f4784..799574df
--- a/test/move-registry-baseline.json
+++ b/test/move-registry-baseline.json
@@@ -7095,11 -7086,7 +7095,12 @@@
"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_LANE_LEAD": "name a configured lane and an existing seat in that lane, or off",
+ "BAD_MESSAGE_KIND": "use --kind question, blocker or decision",
+ "STATUS_IS_ACTIVITY": "keep working on the item; status is board activity, not a shout",
+ "LANE_MESSAGE_ITEM": "omit --kind for an item-specific message",
- "NOT_LANE_LEAD": "ask your named lane lead to send the decision upward"
++ "NOT_LANE_LEAD": "ask your named lane lead to send the decision upward",
+ "RUNNER_WAIT_DEADLINE": "check the runners the message names, or restore local gate capacity with pullboard settings, then retry"
},
"replay": {
"initial": {