Thanks for the report.

As far as Content Translation functionality goes, I don't understand why is this a problem. That's the whole point of showing a notification that the article exists already. Content Translation automatically adds a Wikidata sitelink to a newly translated article. If a good article already exists in the target wiki, then a new translation shouldn't be published. (Publishing an empty translation is also not a good idea.)

All that said, I'm a bit surprised that the Wikibase code just changed the interlanguage link. I'd expect wb.PageConnector() not to replace the link silently by default.

Hello @alanajjar,
I have made slight corrections to the structure of your report and fixed some typos.

Please verify that what I changed is correct :)

In T203544#4558845, @Petar.petkovic wrote:

Please verify that what I changed is correct :)

Hello @Petar.petkovic Thanks for correcting, I appreciate that :)

In T203544#4558837, @Amire80 wrote:

If a good article already exists in the target wiki, then a new translation shouldn't be published. (Publishing an empty translation is also not a good idea.)

Thanks @Amire80
That's exactly what I want to convey!

Well, sometimes it is useful to publish a translation even when such an article already exists, so Content Translation is not blocking it completely, but we do show a warning and let the user decide.

In T203544#4558979, @Amire80 wrote:

Well, sometimes it is useful to publish a translation even when such an article already exists, so Content Translation is not blocking it completely, but we do show a warning and let the user decide.

Of course it's good to let the user decide, but it shouldn't change the interwikilinks in Wikidata automatically from the already existing article to the new one.