Multi-repo coordinated fixes

A bug like “checkout returns 400 with ‘invalid currency’” often spans two repos: the FE sends a malformed shape, the BE accepts a wider range than it should. Mushi’s MultiRepoFixOrchestrator plans and opens one PR per repo for these, keeping the change set coherent and cross-linked.

Setup

In Settings → Repositories, register each repo your project owns:

Field	Example
Repo URL	`https://github.com/acme/checkout-fe`
Role	`frontend`
Default branch	`main`
Path globs	`apps/web/`, `packages/ui/`
Primary?	one repo per project must be primary

The path globs are the routing rule the planner uses: any file the classifier identifies as relevant gets matched to the first repo whose globs cover it. When no glob matches, the file lands in the primary repo.

MultiRepoFixOrchestrator.plan() throws if your project has only one row in project_repos. The admin console automatically picks the right orchestrator based on repo count — you never call it directly unless you’re using the MCP.

How a coordination flows

Coordination flow

1Admin triggers POST /v1/admin/fixes/coordinate — Planner agent produces a task list with a rationale for each repo.

2fix_coordinations row inserted (status=planning). One FixOrchestrator spawned per repo in parallel.

Frontend repo

checkout-fe

acme/checkout-fe

Backend repo

checkout-be

acme/checkout-be

3Each orchestrator opens a PR independently. PR body includes: diff summary, files changed, AI rationale, spec-validation warnings.

4After both PRs are open, linkPRs() posts a cross-link comment on each: "This PR is part of a coordinated fix — see siblings before merging."

5Status reconciler rolls up children → parent fix_coordinations.status (see table below).

All completedsucceeded

Some completed, some failedpartial_success

All failedfailed

Manually stoppedcancelled

Cross-linking PRs

After every child PR is open, the orchestrator posts a cross-link comment on each one:


🤝 Mushi multi-repo coordination

This PR is part of a coordinated fix across multiple repos:

- [frontend] https://github.com/acme/checkout-fe/pull/812
- [backend]  https://github.com/acme/checkout-be/pull/345

Merge order matters when there are FE↔BE contract changes —
review siblings before merging this one.

Reviewers see the full change set without hunting for the sibling — the comment is the single source of truth for the coordination ID.

Inventory traceability

If the root report is linked to an inventory Action node, the inventory_action_node_id flows into every child fix_dispatch_jobs and fix_attempts row. Each orchestrator independently runs validateAgainstSpec() before opening its PR, and a post-PR synthetic probe is queued for the originating Action. The synthetic monitor’s verdict — verified or regressed — appears in the Fixes drawer under each child PR within minutes of merge.

See Inventory and gates → Spec traceability for the full chain.