Multi-subagent code review across security, quality, performance, and architecture

Failure modes

Symptom	Cause	Fix	Severity
`RuntimeWarning: coroutine 'CodeReviewWorkflow.execute' was never awaited`	`execute` called without `await`	It is a coroutine — `await` it or use `asyncio.run`	high
`WorkflowResult.success` is `False`, `error` is `"path argument is required"`	`execute` called with empty or missing `path`	Pass a non-empty `path`	high
`attune workflow run code-quality` errors "unknown workflow"	The slug is `code-review`, not `code-quality`	Run `attune workflow run code-review` (the skill / help topic is `code-quality`)	medium
`error` reads `"Agent SDK unavailable: ..."`	`claude_agent_sdk` is not importable	Install the Agent SDK dependency for the environment	high
`error` reads `"Agent SDK connection failed: ..."`	A `ConnectionError` / `TimeoutError` reaching the SDK	Check connectivity / retry; `transient` is set when a retry is reasonable	medium
Review stops early / partial report	The depth's agent-turn or budget cap was reached	Use a narrower `path`, a shallower `depth`, or accept a deeper (costlier) run	medium
A finding looks like a false positive	Findings are LLM predictions, not verified defects	Confirm against the cited file/line before acting	medium

The async call is easy to get wrong. execute is the only public method and it is a coroutine. Forgetting to await it is the single most common mistake.
The slug differs from the name. The feature, skill, and help topic are code-quality; the workflow slug and MCP tool are code-review. Use code-review for attune workflow run and the MCP call.
Findings are predictions, not proofs. A CRITICAL or HIGH finding means "look here first," not a confirmed defect — and a clean review is not a guarantee. Verify before acting.

Confirm you are awaiting: result = await workflow.execute( path="src/") inside an async def or asyncio.run.
Check result.success; if False, read result.error and result.error_type.
For an "unknown workflow" CLI error, confirm you used the code-review slug.
On an SDK error, inspect result.metadata for the captured sdk_stderr / SDK error kind.
Confirm the scope: result.metadata echoes the path, depth, and max_turns.