Augemented diff missing coordinates for some way nodes

[simonpoole]

See https://overpass-api.de/api/interpreter?data=[adiff:"2025-07-16T19:52:21Z","2025-07-16T19:52:23Z"];(node(bbox)(changed);way(bbox)(changed););out meta geom(bbox);&bbox=8.0764287,47.373149,8.0798153,47.3754722 for example way 43339527

<new>
  <way id="43339527" version="8" timestamp="2025-07-16T15:33:33Z" changeset="169020060" uid="92387" user="SimonPoole">
    <bounds minlat="47.3744023" minlon="8.0763878" maxlat="47.3753600" maxlon="8.0769630"/>
    <nd ref="303917588"/>
    <nd ref="13001508465"/>
    <nd ref="544897774"/>
    <nd ref="544897218"/>
    <nd ref="13001508472"/>
    <nd ref="1193548287" lat="47.3753600" lon="8.0763878"/>
...

Maybe I'm missing something, but the documentation https://wiki.openstreetmap.org/wiki/Overpass_API/Augmented_Diffs#The_augmented_diff_API_call says All nd elements inside of way elements contain additional lat and lon attributes:

[drolbr]

Thank you for reporting the issue.

The URL says: bbox=8.0764287,47.373149,8.0798153,47.3754722, and the other coordinates of way 43339527 are outside of that bounding box.

Indeed, it is next to impossible to find that behaviour in the documentation. I have to figure out who relies on this before changing it. One use use case are relations where one definitely does not want entire relation geometry for every change. However, the overhead for ways should be an acceptable amount.

[simonpoole]

I have to figure out who relies on this before changing it.

I don't think you have to change the behaviour, just document it. Nobody will be relying on the currently documented behaviour because that is literally not what it does.