monorepo-coordinationlisted

# Purpose Plan and sequence changes that span multiple repositories (or multiple monorepo apps/packages) so they land in the correct order, with CI-probe-enforced operator gates and post-merge validation of the whole system. Done when every repo is phased, each MR/PR carries dependency arrows and failure modes, and every operator step has a probe. # Rules - Read the repo shape from `${CLAUDE_PROJECT_DIR}/.claude/project.json` (`repos`, `monorepo`) before planning — the phase model is identical for both shapes; only merge mechanics differ. - Merge order follows the phase model: 1 Foundation → 2 Operator action → 3 Wire consumers → 4 Consume. Never wire before foundation. - Every operator step gets a CI probe that fails if skipped — MR prose alone is never a gate. - When a contracted cross-service boundary changes, read the living contract document FIRST (see `api-contract`) and place its update no later than the emitter change. - Each MR is individually revert-safe; its description carries Depends on, Blocks, Operator steps, and Failure mode if merged out of order. - Use durable identifiers (file paths), never transient MR numbers; immutable digests, never mutable tags, in cross-repo handoffs. # Resources - Read `resources/phase-model-and-procedure.md` when building the plan — repo-shape detection, when (not) to use, inputs/outputs, the output template, and the six-step procedure with MR and CI-probe boilerplate. - Read `resources/checks-and-examples.md` before returning