weird interaction between tramp-mode and annotate-mode

[cage]

Hi!

I am a co-maintainer of annotate.el, a package to add textual notes to
a file without modify it.

https://github.com/bastibe/annotate.el

I got, a few days ago, an  interesting issue report about a crash that
only occurs when annotating and editing a file visited using TRAMP.

Below a link that contains the thread:

https://github.com/bastibe/annotate.el/issues/139

in particular  this message contains  a bunch  of code (from  the kind
user that signaled the bug) to reproduce the problem:

https://github.com/bastibe/annotate.el/issues/139#issuecomment-1294381098

Seems  that, for  some  reasons,  tramp is  invoking  a function  from
annotate-mode  (``annotate--remove-annotation-property'') on  a buffer
different from the one where annotate  mode is active. Said buffer has
a name like: ``*tramp/ssh something*''

Please check the first message as  it contains both the stacktrace and
useful information at the end.

I  used   a  workaround  (prevent   the  function  above  to   run  if
``annotate-mode'' is bound to nil), but i do not like this solution.

In  brief, i  am asking  for suggestion,  why TRAMP  is visiting  that
buffer? And why is calling that annotate function (that is supposed to
be call to fontify the annotated buffer when the latter is modified)?

Can calling ``annotate--remove-annotation-property''  be prevented? Am
I missing a call to a macro like ``with-current-buffer'' somewhere?

And,  out  of curiosity,  what  the  buffer ``*tramp/ssh  something*''
contains? Seems like a register for TRAMP.

Thanks in advance!
C.