The problem with writing issues is that they are good if the potential solution requires investigation, discussion or documentation on why certain way of handling was chosen. But in cases like point 4 it is actually easier and faster if I make changes myself than to describe it for others to do. I'd have done that long ago if I had an environment ready where I could test such changes before proposing them (and the last time I did anything on front-end was 25 years ago). So next best thing is to stand on top of the dev who can show result of the changes locally before they are committed :o)
By the way, point 4 issue is only here because people that made those visualizers in the first place are not actually using Hive, so they are not familiar with fine details. I'm sure it does not apply to you.