worst-case-lookup

# Worst Case Lookup Overall verdict = most severe domain/item value, on the caller's own scale. Merges what were originally 3 separate SOPs (RoB2-aggregate, ROBINS-I-aggregate, AMSTAR-2-aggregate) per coverage-audit M10's finding that they share one algorithm (worst-case-taking) differing only in value domain and, for AMSTAR-2, an extra pre-filter step — the same parameterization principle already used for unit-classification's label_set parameter, applied consistently here. ## Execution Subagent — spawned via spawn-agent skill. ## Two Distinct Callers — Do Not Assume Which Unlike most SOPs in this package, this one is called from two different places in the graph with two different input shapes (`domain_judgments` vs `checklist_result`). The prompt's Step 1 instruction to identify which was received before proceeding is load-bearing — applying RoB2's worst-case rule to AMSTAR-2's input (or vice versa) silently produces a wrong answer, not an error. <!-- BEGIN available-tables (generated) --> ## Available SOPs | SOP | When to use | | --- | --- | | spawn-agent | Spawn a customized CC subagent with full MCP tool access. | <!-- END available-tables (generated) -->