You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Merge fix-integration-copilot
* Merge fix-supervisor-loop
* fix: add plan merging state transition and improve PR message generation
- Transition plan status to merging while merge train is active
- Add merging→running and merging→paused to valid plan transitions
- Improve orchestrator createPR with job status table and real test config
- Improve mc_pr tool with PR template lookup and conventional commit titles
- Always include Mission Control attribution in PR bodies
* fix: remove hardcoded feat: prefix from PR titles, let callers control format
Plan name is used directly as the PR title. Tool descriptions and README
updated to guide agents toward Conventional Commits format. Also fixes
integration branch format in README docs (mc/integration/ → mc/integration-).
|`title`|`string`| No | Job name| PR title — use [Conventional Commits](https://www.conventionalcommits.org/) format (e.g. `feat: add login`, `fix: resolve timeout`)|
411
+
|`body`|`string`| No |PR template or auto-generated | PR body. If omitted, uses `.github/pull_request_template.md` if found, otherwise generates a summary.|
412
412
|`draft`|`boolean`| No |`false`| Create as draft PR |
413
413
414
414
#### `mc_sync`
@@ -443,7 +443,7 @@ Create and start a multi-job orchestrated plan.
|`name`|`string`| Yes | — | Plan name — used as the PR title, so use [Conventional Commits](https://www.conventionalcommits.org/) format (e.g. `feat: add search`, `fix: resolve auth bugs`) |
447
447
|`jobs`|`JobSpec[]`| Yes | — | Array of job definitions (see below) |
448
448
|`mode`|`"autopilot"`\|`"copilot"`\|`"supervisor"`| No |`"autopilot"`| Execution mode |
449
449
|`placement`|`"session"`\|`"window"`| No | Config default | tmux placement for all jobs in this plan |
@@ -474,7 +474,7 @@ Create and start a multi-job orchestrated plan.
474
474
mc_plan
475
475
│
476
476
├─ Validate (unique names, valid deps, no circular deps)
@@ -534,7 +534,7 @@ This example uses `mc_plan` instead of four separate `mc_launch` calls because:
534
534
AI: I'll create a plan for the dashboard feature with proper dependencies.
535
535
536
536
→ mc_plan(
537
-
name: "dashboard-feature",
537
+
name: "feat: analytics dashboard",
538
538
mode: "autopilot",
539
539
jobs: [
540
540
{
@@ -571,7 +571,7 @@ Result:
571
571
572
572
### Merge Train
573
573
574
-
The Merge Train is the engine behind plan integration. Each completed job's branch is merged into a dedicated **integration branch** (`mc/integration/{plan-id}`):
574
+
The Merge Train is the engine behind plan integration. Each completed job's branch is merged into a dedicated **integration branch** (`mc/integration-{plan-id}`):
575
575
576
576
1.**Merge** — `git merge --no-ff {job-branch}` into the integration worktree
577
577
2.**Test** — If a `testCommand` is configured (or detected from `package.json`), it runs after each merge
'Create and start a multi-job orchestrated plan with dependency management',
14
14
args: {
15
-
name: tool.schema.string().describe('Plan name'),
15
+
name: tool.schema.string().describe('Plan name — used as the PR title. Use Conventional Commits format (e.g. "feat: add search", "fix: resolve auth bugs").'),
0 commit comments