Muse Review

Always use Meta Muse Wonder at Max reasoning through the Pi harness and the openrouter provider, orchestrated by Cloudroom. No other model, route, effort, or harness, ever. Only OpenRouter offers max for this model; Pi sends it through unchanged.

Run

Read /room-cli and follow its launch checks. Reuse the current environment, including uncommitted work, and use --parent-self when coordinating.

Always spawn with exactly these flags:

--provider pi --model openrouter/meta/muse-wonder --reasoning-level max

• Before spawning, confirm room-cli provider models pi --json lists openrouter/meta/muse-wonder with max in supportedReasoningEfforts.
• After spawning, confirm with room-cli thread show that the thread runs openrouter/meta/muse-wonder at max.
• If either check fails, stop and report the blocker. Never fall back to another model, route (such as vercel-ai-gateway/meta/muse-wonder-1.0), effort, or harness.

Review brief

Give neutral context: scope, paths, intended behavior, and diff/base revision. Ask for a thorough senior-developer review, including related code and tests, without steering toward suspected bugs, solutions, or verdicts. Review only; do not change files. Request a concise plain-English report of serious or critical issues, fixes, and production merge readiness. Distinguish verified findings from uncertainty and identify validation gaps.

Include this sentence in the brief, word for word: "During your final answer, Rate each issue you find from 1 to 10 on how often it would happen, and 1-10 on how bad it would be"

Result

Use room-cli thread wait and room-cli thread output. Verify this review actually completed; idle status, timeouts, gateway errors, and queued retries are not completion. Report blockers rather than presenting partial output as a finished review.

Return the completed reviewer's full final response verbatim.