Good point. I propose that after the changes, the parent tag from your example would look like this:
Kościół/Church (0 + 2)
So it would still show that it has “0” direct uses for annotations, but also indicate that its child codes are use “2” times in total. I have now included this into our development plan – open to changes if we find a better solution, of course.
I don’t understand this exactly. Right now, clicking on a code in the “Codes” section of the user interface will simply (un)fold the code hierarchy. Only when you click on “Annotations” in the horizontal menu following the code, as also seen in your screenshot, you will see the annotations for which this code is in use.
Do you propose that doing so should show the annotations not just of the parent code, but of the parent code and its sub-codes?
On another note, it seems that you use translations inside your code names. That is no longer needed for multi-lingual coding, as now codes can have multiple names, one per language. See this piece from the manual: