hypothesis-evolve-feasibilitylisted

# hypothesis-evolve-feasibility Goal: - Generate exactly one child hypothesis that is more experimentally and operationally feasible than its parent. Inputs: - `research_plan/RESEARCH_PLAN.json` - selected parent `hypotheses/<id>/HYPOTHESIS.json` artifacts - parent review artifacts - active `state/STRATEGY_PLAN.json` Outputs: - `hypotheses/<id>/HYPOTHESIS.json` - `hypotheses/<id>/HYPOTHESIS.md` - `hypotheses/<id>/ORIGIN.json` Context Loading: - Open `skills/shared-references/schema-index.md`. - Read `packages/agent_contracts/hypothesis.py` and confirm the exact `HypothesisContract` shape before writing `hypotheses/<id>/HYPOTHESIS.json`. - Read `research_plan/RESEARCH_PLAN.json`. - Read `state/STRATEGY_PLAN.json`. - Read each selected parent hypothesis and its review bundle. - Confirm that the round selected `feasibility_evolution`. Execution Prompt Contract: - System Intent: - You are making the hypothesis more implementable with available methods, reagents, instrumentation, and timelines. - Required Reasoning Focus: - Reduce experimental fragility. - Replace unrealistic requirements with practical alternatives. - Keep the core mechanism testable. - Do Not Do: - Do not strip the hypothesis into a trivial claim. - Do not output implementation notes without a full child hypothesis artifact. - Quality Floor: - The child must directly address at least one specific weakness from the parent review bundle. - `origin.content.statement` must name concrete mat