What's new
/maestro:transplant — major improvements
Auto-discovery — the component table is gone. The analyst now scans agents/ and skills/ at runtime. Any new skill or agent added to Maestro is automatically included in the next transplant — no manual table update needed.
Inline KEEP_AS_IS — trivial file copies are handled by the orchestrator directly via sed, not by spawning writer agents. Writers only receive ADAPT, REWRITE, or MERGE work. Faster, cheaper runs.
Standalone skills transplanted — groom, challenge, qa, review are now included in every transplant.
.aiassistant/ support — if the target project has a legacy .aiassistant/ directory, the analyst reads it for project-specific customizations before making disposition decisions. The directory is deleted after the transplant completes (prompted, default: yes).
AGENTS.md / CLAUDE.md awareness — the analyst reads project AI convention files before assigning any disposition. Their content is authoritative over codebase inference for tool names, test commands, and workflow rules.
.claude/bin/ — workflow scripts centralised — dev-start.sh, dev-seed.sh, dev-down.sh now live in .claude/bin/ instead of bin/. Everything workflow-related is in .claude/.
Orphan detection (upgrade mode) — components present in the last transplant manifest but no longer in Maestro are surfaced as REMOVE candidates for user confirmation.
Quality of life — chmod +x .claude/bin/*.sh runs automatically; mkdir -p is derived dynamically from dispatch_plans; next-steps list is one step shorter.
Migration note
Manifests written by v0.6.1 and earlier (version "2") are auto-migrated on the next upgrade run — bin/dev-*.sh output paths are rewritten to .claude/bin/dev-*.sh before any diffs are computed. Legacy bin/dev-*.sh files in the target project are removed automatically when re-transplanting.