At the moment, deploying an asset-mapper enabled app requires knowning about the asset-map:compile command.
And switching back and forth from the dev to the prod env requires knowing how to undo what this command did to get a working dev env back from prod (and running the command in the opposite direction.)

This creates DX issues like #59065.

I was thinking about changing the command to remove the assets files in debug mode. This would enable adding it to the default composer.json.

But it wouldn't fix DX for the back-n-forth between dev/prod. A cache-warmer would.

Is there any reasons why we didn't go with a cache-warmer? I checked #50112 but didn't find any rationale for/against this.