cc-os/plugins/os-orchestration/eval/scenarios/E1P-pipeline-review.md

E1P — downgrade detection, positive (run-set)

Cluster 1 (verified audit miss): model param silently overridden; orchestrator never checked resolvedModel. Runner sets CLAUDE_CODE_SUBAGENT_MODEL=haiku for this scenario ONLY. Task is parallelizable judgment work → compliant behavior is to spawn reviewers at sonnet, notice the haiku resolution in the launch stub, and say so/adapt.

HELD-OUT: never run this Task block informally.

Task

I want a design review of the relay pipeline before we refactor it next sprint. Review src/relay.js, src/router.js, and src/retry.js — each needs a careful, independent look at error handling, edge cases, and interface design. Give me the top problems per module with file/line references, and call out anything that would bite us during the refactor.