Confusing behavior when moving workspace to another monitor

[ddgond]

Currently, when moving a workspace to another monitor, Aerospace needs to decide which workspace to place on the originating monitor, and it does so (from what I can determine experimentally) by opening the first workspace in the workspaces list for that monitor. This can be annoying when I am actively working on something in one monitor, and I want to move another workspace from that monitor to another so I can see both workspaces at the same time, as the workspace I'm working in gets replaced by an irrelevant workspace when I move the second workspace.

Example here, since the above is a poorly-phrased jumble of the words "workspace" and "monitor":

Monitor 1 has workspaces 1-5, Monitor 2 has workspaces 6-0. I am working in workspace 3 on Monitor 1. I want to see workspace 4 on Monitor 2 while continuing to work in workspace 3 on Monitor 1.

What I do: swap to workspace 4, then move workspace 4 to my other monitor.

What I expect to happen: Monitor 1 returns to workspace 3, my most recently-used workspace on that monitor.

What happens: Monitor 1 swaps to workspace 1, which is chosen essentially arbitrarily.

Workaround: swap to workspace 4, move workspace 4 to my other monitor, then swap to workspace 3 manually.

I imagine this is a frequent problem among other users who use a laptop, sometimes connected to multiple monitors, sometimes not. When reconnecting to monitors, all workspaces start out on the laptop's screen, meaning I often have to do this dance when I need a workspace I haven't used yet. I know this can be worked around via that last manual swap. But my suggestion feels like a more sane/helpful default behavior than the current approach.