It could have an "edit only visible in Jumble" tag in addition to having the "edited" tag.
Discussion
The main issue is that many other clients can’t display this information. On those clients, users would only see the unedited content.
An edit could simply be a different type of quote. Clients who support editing in this model would understand that it's not a regular quote but an edit, and would render it in a way that makes it look like a conventional edit to users. During the editing process, there would be an "Edited" marker, written in text, that wouldn't be visible to users and couldn't be deleted. This "Edited" text, when the note is published, wouldn't be visible to users of clients who support it, only to those who don't. This way, users of those clients would know that the quote was made to correct something from the previous note.
Yes, if an edit is implemented as a special kind of quote and is still a kind-1 event, then it would indeed be more compatible than Amethyst’s approach. However, it would also make the already complex semantics of kind-1 events even more complicated.
There’s an ongoing discussion about editing here, which you might want to check out: https://github.com/nostr-protocol/nips/pull/1090
The feature itself is quite controversial. Personally, I’m not in favor of editable notes at the moment. I consider them harmful overall, even if an "edited" marker is added.
I will read it when get some time, thx