hypothesis-review-summarylisted

# hypothesis-review-summary Goal: - Summarize the completed reviews for a hypothesis. Inputs: - `hypotheses/<id>/HYPOTHESIS.json` - completed review artifacts under `hypotheses/<id>/REVIEW/` Outputs: - `hypotheses/<id>/REVIEW/REVIEW_SUMMARY.json` Context Loading: - Read `hypotheses/<id>/HYPOTHESIS.json`. - Read all completed review artifacts under `hypotheses/<id>/REVIEW/`. - Focus on synthesizing the strongest strengths, weaknesses, and recommended next actions across those reviews. Execution Prompt Contract: - System Intent: - You are synthesizing the completed review stack into a compact downstream summary. - Required Reasoning Focus: - Deduplicate repeated points across review stages. - Preserve the most important strengths, weaknesses, and action items. - Prefer high-signal synthesis over exhaustive restatement. - Do Not Do: - Do not summarize reviews that do not exist. - Do not copy every review point verbatim. - Do not invent a new evaluation framework at summary time. - Review Quality Floor: - A `status = completed` review summary must synthesize concrete findings from completed review stages. - Include the strongest actionable strength, weakness, or next-step implication when those appear in prior reviews. - Do not use placeholder summary phrases such as `Viable evolved hypothesis`, `Refined from parent`, `strong candidate`, or `needs validation` as substantive summary content. - Output Shape: - Produce the exact `ReviewSummaryContract