Pipeline iterativity: scope↔arch revision loops on evolving requirements

Remaining slice after e42e75b (entry bounces fixed) and v2.0 evidence gates: mid-design requirement changes still assume clean cascades (tactify-style sessions showed 7 scope passes). Watch real usage; design revision-loop support if update stances prove insufficient.

🤖 Generated with [Claude Code](https://claude.com/claude-code)