Brandportal Tag publishing - cleaning up old tags

Update tldr:
This TAG situation is getting more and more confusing and I suggest that i get in touch with somebody at Adobe about this. 

Update in detail:
It feels like the tagging system - how to manage tags, how to publish them, how to merge and delete them, how to change values in the system accordingly - is a bit broken. If it is as intended, at least it is is not what it seems to be.

Let me explain, or what Decard Cain used to say, stay a while and listen...:
Once upon a time, i was instructed to do all my changes in the DEVeloper environment, then create packages which i then have to sent to our Developer, so he can put the content of the package into our Master Branch, so that the next deployment will not reset the changes.

This was also done for the tags. (Now we reversed that policy, since tags had to change way more often than deployments were done)

Lets start by saying that i fully understand that the "merge tag" functionality can not work as you might hope by uploading packages and then deploying those packages.
But the "merge" function does also not really work if you do it in the PRODuction enviroment - therefore it does not really "really" work at all. It provides the function, but creates a lot of broken assets in the process.

You see, a tag that is created, will be written into the metadata of assets and then it stays there.
You can merge that tag into something else, your metadata within the asset is not changed.
You can rename a tag... sure... but this gets confusing very fast and I would not suggest this approach, and even if you do - this will not solve all the tags that have to move within the namespace- or tag structure.

So, as soon as you update your tagging structure, you will create broken tags in a lot of assets.
This becomes not visible in a warning!
(Forget the Brand Portal Tag publishing for now... this will become interesting later ... in a bad way)
You will notice that something is off with your tags within the asset-details or when you export your cq:tags metadata via a csv export.
This will then be your best approach to repair your assets. (Maybe there is a better, i haven't found one yet).
Now here comes my suggestion:
Wouldn't it make more sense that the tag management also has some impact on changes within the tag values of the assets? You merge a tag into something else, the system needs to do something with assets that hold this old tag. It also should check if this tag is published to BP and depublishes it. Otherwise you land where I currently am - where I have to recreate old tags, to depublish them in the BP, to delete them right after ... in the PROD environment.
Dear Adobe - this current way of managing tags creates a lot of problems.
Lets have a talk about it. You have my number 🙂