Funny enough, this is exactly the example I mention in the talk (isEditing) and the right thing for the model to do is to just split it into distinct component trees from the shared parts
Drop isEditing, and just recompose the internals in a separate <EditMessage />
Curious if Opus will pick that up. I might add some more aggressive notes to another rule in the skill.