By default, Developer Edition is meant to use a separate profile so that it can be run side by side out of the box. @Tyler-Atl, were you using it side by side successfully before, and then it changed after updating?
Thanks for the replies. It looks like when I migrated to my new Macbook, my old Firefox profiles were corrupted, so regular Firefox was using the ‘default-developer-edition’ profile.
As suggested, I used the profile manager to sort it out. I renamed the working profile to ‘default’ and then launched the Developer Edition (which must have created a new dev edition profile): /Applications/Firefox.app/Contents/MacOS/firefox-bin -profilemanager
Adding a comment here in case anyone else runs into my variant of this issue.
I had FF beta channel installed side-by-side with the developer edition on a Mac, and last week it seemed like the beta channel install had flushed my profile data. But I went to open developer edition just now, ran into the issue mentioned above, and discovered that the beta channel had just switched to opening the developer edition profile by default somehow.