v1.0.3 — Marker collision fix, intro double-parens fix, redundant test-command fix
Three cosmetic bugs surfaced when testing v1.0.2 on a real project.
CLAUDE.md heading was garbled
The block heading was rendered as `## 🚨 Multi-Agent Coordinationnation -->` instead of `## 🚨 Multi-Agent Coordination`. Root cause: the legacy BEGIN marker (``) shared the word "coordination" with the next line's heading, and Claude's write path was merging the tails together.
· Fix: switched markers to `` and `` — distinct, short, no shared vocabulary with the heading.
· A blank line was added between the BEGIN marker and the heading to prevent any further visual merging during write.
· The wizard still recognizes the legacy marker format so existing v1.0.0-v1.0.2 installs upgrade cleanly on the next `/multi-agent-init`.
Developer intro had double-parens
Lines read: "You implement tasks dispatched by the Planner (the Planner (P))." Root cause: the v1.0.1 `T4 -> "the Planner (P)"` replace_all was too greedy and inserted the long form into contexts that already said "Planner".
· Fix: rewrote the developer intro phrasing to use "Planner (\`P\`)" once, no nesting.
Redundant test command in intros
When the user reuses the build command for tests (common when there's no test script in package.json), the intro printed "run \`npm run build\` and \`npm run build\` until both pass" — nonsense.
· Fix: wizard now detects `build_command == test_command` and collapses to single-command form: "run \`npm run build\` until it passes."
Self-check list expanded
Step 9 (intro output) now has a longer pre-flight check that catches all three bugs before declaring "setup complete". The wizard re-prints any block that fails a check.
Upgrade
```
/plugin marketplace update multi-agent-coordination
/plugin update multi-agent-coordination
```
Existing projects with the legacy CLAUDE.md markers will pick up the new format on the next `/multi-agent-init` (pick "Overwrite from scratch" — the wizard recognizes the old markers and replaces cleanly).