$> ls /nix/store/5v1zvr531ndsd960g5iplb8g5ym7hxri-hamster-time-tracker-3.0.2/bin -A
hamster  .hamster-wrapped  ..hamster-wrapped-wrapped

..hamster-wrapped-wrapped is an interesting name, but I guess it's up to the wrappers and not the individual package to do this saner when wrappers are combined with each other. 🙃

$> ls /nix/store/5v1zvr531ndsd960g5iplb8g5ym7hxri-hamster-time-tracker-3.0.2/bin -A
hamster  .hamster-wrapped  ..hamster-wrapped-wrapped

..hamster-wrapped-wrapped is an interesting name, but I guess it's up to the wrappers and not the individual package to do this saner when wrappers are combined with each other. upside_down_face

Alright, I was wrong; It seems that at least for now, it actually is the package's responsibility to combine the wrappers properly. (See also #90051 (comment).)

For Python applications, the manual advises to do that with

{
  #...

  dontWrapGApps = true;

  # Arguments to be passed to `makeWrapper`, only used by buildPython*
  preFixup = ''
    makeWrapperArgs+=("''${gappsWrapperArgs[@]}")
  '';

Thanks.