strategy-routerlisted

# strategy-router Goal: - Produce the current `state/STRATEGY_PLAN.json` bundle for configuration, generation, review, evolution, or overview routing. Inputs: - current run-local artifacts - `RUN_POLICY.yaml` - `state/RESOLVED_RUN_CONFIG.json` - optional `state/PIPELINE_STATE.json` - optional `state/CURRENT_STAGE.json` - optional `state/EVOLUTION_STATE.json` - optional `state/COMPLETION_DECISION.json` Outputs: - updated `state/STRATEGY_PLAN.json` - appended `state/STRATEGY_DECISIONS.jsonl` Context Loading: - Open `skills/shared-references/schema-index.md`. - Read `packages/agent_contracts/strategy_plan.py` and confirm the exact `StrategyPlanContract` shape before writing `state/STRATEGY_PLAN.json`. - Read `packages/agent_contracts/pipeline_control.py` when completion or evolution signals are present. - Read persisted stage information from `state/PIPELINE_STATE.json` and `state/CURRENT_STAGE.json` before inferring a route. Execution Contract: - This skill is deterministic and must not call an LLM. - Use `python -m tools.policy.plan_strategy <run_dir> [--phase <Configuration|Generation|Evolution|Insights from Reviews|Proximity|Ranking|Research Overview>]` as the canonical invocation surface. - The underlying implementation lives in `tools/policy/plan_strategy.py`. - The router must honor the effective run policy, resolved numeric config, persisted stage artifacts, and completion advisories while still emitting one explicit next-action artifact. - When `research_plan/