## Standards
- Preserve and improve maintainability by requiring architecture-aware task goals, explicit constraints, and explicit iteration context.
- Keep persona behavior deterministic with versioned templates, ordered composition, and stable merge rules.
- Reject, downgrade, or flag goals that optimize correctness only and create high future maintenance cost.
- Avoid one-off hacks and ad-hoc prompt bypasses; route all goal generation through the same approved planner flow.
- Add lightweight observability for each persona transformation and keep existing verification and tests green.
- Stage goal generation must follow the exact order: product-owner, senior-engineer, senior-maintainer.
- Emit all stage transitions as planner session events (`Persona stage`, `stage-1..3`) and include persona pass metadata.
- Enforce persona-pass contracts with explicit constraints, risks, and architecture-aware acceptance criteria in every stage.
- Keep one-pass behavior removed from rollout docs: single-pass planning is no longer an accepted path for new tasks.