The reason why I consider it may be potentially desirable for communicating with prompters is that prompters usually need a way to verify the model has done what they asked, but without necessarily needing to review all the code or very long runs of text. They only need a bare minimum to know that their requirement has been met and not a full explanation of everything, so the super terse and efficient way of communicating how the constraints are implemented can be helpful. I understand that a lot of prompters don't need this style, or that some people just hate it unconditionally and need it to be different, that's just my guess for why it might've been reinforced during training.

Experienced prompters also typically know what they're doing, so they don't need the full explanation, only the bare minimum details that apply to this particular case. Again, users are different here, but the model doesn't know the difference in order to write it, so that's another way this can end up happening.

… are there many lighthouses in the Labrador interior?

Looks like a bug with the view origin point being mis-matched with what the view's actually focused on - maybe high-DPI scale mis-match?

https://www.lhg.is/media/sjomaelingar_islands/Vitaskra_31101...