Should Plot.maxX consume the reverse option?

See https://observablehq.com/@observablehq/surprising-reverse-gets-eaten: if you have

Plot.stackY(
  Plot.selectMaxX({
    order: "y",
    reverse: true
  }))

reverse: true is "eaten" by the select transform, and doesn't do anything.

Applying maxX after stackY works as expected:

Plot.selectMaxX(
  Plot.stackY({
    order: "y",
    reverse: true
  }))

I'm not sure if this is fixable (we could want all the selection transforms to pass sort and reverse untouched?), but it's at least surprising.

Start by tracing the Plot.selectMaxX and Plot.stackY entry points using the two examples in the issue, then inspect how the select transform handles order and reverse. Compare both transform orderings and define done as reverse behaving consistently with the documented or intended selection semantics.