v0.5.1 — Transplant: config-free workflow & QA pass

What changed

Transplant pipeline — breaking improvements

Config file eliminated. Transplanted workflows no longer generate or depend on maestro.json. The orchestrator now has a ## Project Config block with values baked in at transplant time (REPO, TEMP_ROOT, BASE_BRANCH, test/lint/boot commands). Agents receive everything via prompt injection — no file reads at runtime.

TEMP_ROOT is now project-specific. The project interview asks for the working temp directory name (default .ai, e.g. .TemporaryItems). The analyst also checks .gitignore for existing patterns.

Universal de-brand pass. Every transplanted file (regardless of disposition) now strips Maestro config reads, maestro.json path references, and Maestro branding from prose.

QA pass added (Claude Opus). After all writer agents complete, a transplant-qa agent runs 6 checks — no Maestro references, no runtime config reads, orchestrator has constants block, WP content stripped for non-WP projects, stack consistency, and FIXME scan. A red verdict triggers targeted re-work on flagged components (max 2 rounds).

Cleanup prompt added. After QA green light, users are asked whether to remove upgrade artifacts (transplant-refs/, manifest, context doc). Choosing yes leaves a fully self-contained workflow with no Maestro footprint.

Upgrading

Re-run /maestro:transplant <target> on any previously transplanted project to get the config-free layout. The upgrade path will detect and merge your team's customizations.