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
docs(api): init reports how each MCP client was set up [A9,I1]
Corey Olsona8080f29a914
diff --git a/docs/api.md b/docs/api.mdindex fb1cd263..b09d3fdb 100644--- a/docs/api.md+++ b/docs/api.md@@ -78,7 +78,7 @@ For example: `flow: review wait average 61 min (1 measured; > 60 min); bottlenec| --- | --- || `help` | `version:number`, `help:string` || `version` | `version:number`, `release:string` |-| `init` | `version:number`, `root:string`, `notes:array`, `proposedLanes:array` |+| `init` | `version:number`, `root:string`, `notes:array`, `proposedLanes:array`, `mcp:object` || `hooks` | `version:number`, `notes:array` || `join` | `version:number`, `agent:string`, `lane:string`, `route:string`, `path:string`, `model:string`, `displayName:string` || `takeover` | `version:number`, `agent:string`, `path:string` |@@ -452,6 +452,8 @@ Decision moves keep the CLI's routing: `shout` with `args.decision: true` may omOnly the coordinator runs `spec apply`. It preflights every pending row against the exact source text, refusing stale decisions before writing any file. Approval changes the status to `approved`; decline changes it to `wont` with the person's reason as the row text, preserving trailing fields. SSH-enabled approvals carry one signed `row-decision` receipt binding the file, source, replacement, decision, reason and row text. Apply copies that same receipt into `.pullboard/signoffs.jsonl`; it remains a current exact-text sign-off. Commit the changed files and receipts together.+`init --json` reports `mcp: { claude, codex }`, each `added`, `kept` (already there) or `manual`. Codex is `manual` when `.codex/config.toml` writes `mcp_servers` as an inline table: TOML cannot extend that table from outside it, so init leaves the file byte-identical and prints the exact `[mcp_servers.pullboard]` block for the person to add.+`init` and `blueprint add` take `--blueprint` more than once, and the blueprints land in the order given. A board takes at most one product blueprint and one architecture blueprint, and any number of practice and beyond-code ones; a second product or architecture blueprint is refused with `BLUEPRINT_KIND_TAKEN`, naming both, before anything is written, whether the first is named in the same command or already on the board. Every blueprint leaves `<!-- pullboard-blueprint-kind <name> <kind or none> -->` beside its rows, which is how a later command finds it. A blueprint an older Pullboard added has its marker alone: its kind is read from the bundled file of that name, else from `<name>.json` or `<name>.blueprint.json` at the repo root; failing both, its kind is unknown, and a product or architecture blueprint is refused with `BLUEPRINT_KIND_TAKEN` naming both until the person records the kind by adding that blueprint's file again. Adding the blueprint the board already has again changes nothing but that kind line and is no clash. A rule or question whose row text an earlier blueprint in the same command drafted is drafted once: the later blueprint cites that row and lists it in `shared` as `{ key, id }`. Each starter item in `items` carries `blueprint`, the name of the blueprint that filed it, and its add appends a `note` fact `blueprint starter: {"blueprint":"<name>","version":<version>,"key":"<key>"}` to the item. With several blueprints, `blueprint add` returns the first blueprint's fields with every blueprint's `rows`, `items`, `proposedLanes` and `checksNotRun`, and each one's own result in `blueprints`; `init` returns the first in `blueprint` and all of them in `blueprints`.To answer a pending question row (`<ask>: <default>. Choices: a, b.`, as `blueprint add` writes it), the person runs `spec answer <id> "<choice or text>"`, or the local view sends `spec-answer` with `args: {row: "B1", answer: "Postgres"}`. A listed choice matches in any case and keeps its listed spelling; other text joins the choices last. It refuses agent shells, agent worktrees and the API channel, records the same exact-row approval receipt, whose JSON `decisions` carry an `answer` read back from the signed text (never stored on its own), and the row leaves pending when the coordinator runs `spec apply`. `spec check` errors on a question that was pending at the trunk tip and now differs with no matching person decision.diff --git a/src/init-finish.js b/src/init-finish.jsindex 9243ea2c..d15d83f4 100644--- a/src/init-finish.js+++ b/src/init-finish.js@@ -26,7 +26,10 @@ import {tryGit,} from './git.js';import { loadConfig } from './config.js';-import { CODEX_MANUAL_NOTE, mcpSetup } from './init.js';+import {+ CODEX_MANUAL_NOTE,+ mcpSetup,+} from './init.js';import {alreadyAddedLine,initWaitingRows,