oma-orchestrator

# Orchestrator - Automated Multi-Agent Coordinator ## Scheduling ### Goal Automatically orchestrate multi-agent execution with task decomposition, native/fallback dispatch, memory coordination, progress monitoring, verification, QA cross-review, retry, and result collection. ### Intent signature - User asks to orchestrate, run in parallel, automate multi-agent execution, or coordinate full-stack work end to end. - Task requires multiple specialist agents and a persistent review/remediation loop. ### When to use - Complex feature requires multiple specialized agents working in parallel - User wants automated execution without manually spawning agents - Full-stack implementation spanning backend, frontend, mobile, and QA - User says "run it automatically", "run in parallel", or similar automation requests ### When NOT to use - Simple single-domain task -> use the specific agent directly - User wants step-by-step manual control -> use oma-coordination - Quick bug fixes or minor changes ### Expected inputs - Complex feature or workflow request - Project config, model/vendor routing, agent types, task constraints, and workspace/session needs - Acceptance criteria and verification expectations ### Expected outputs - Orchestrator session state, task board, progress files, result files, and final summary - Specialist agent outputs after mechanical checks, automated verify, and QA cross-review - Review history and retry/remediation status when loops fail ### Dependencies - `.a...