> It's down to you to tell it when it's time to re-engineer.

> without excessive, and very often forgotten, instructions to do so.

It forgets, within long sessions. I'm still seeing Opus 5.5 implement workarounds for bugs it created within its own session, even with explicit, and plentiful, instructions and global memories that it's time to re-engineer.

But to your point, yes, multiple rounds are required. My point is that this is going to eventually hold development back.

Just don't use long sessions and always start a new one to check for bugs/divergence before you commit.