Vigilans

I would have to say some issues listed here are really "hijacked" by other issues. Though some issues are indeed potentially used in a lot of redstone contraptions, but there are others that make complete sense to redstone users if fixed.

Just like MC-250307 (Block material/note block instrument), this behavior restricts the possibilty of note block based block sorter, that half of its functionality is blocked due to the incorrect redstone signal triggered by moving piston block.

This behavior could have been easily fixed by ignoring the instrument update from moving piston block in note block's implementation, just along with some other note block updates introduced in 1.19 (and thus made possible to a efficient clay-based mud farm), but after placing it in this general issue, it is really "hijacked" by other issues that contains side effect and thus prevented from being fixed forever if no such "community consensus" could be reached.

Additional note: this behavior makes the redstone block sorter in https://www.youtube.com/watch?v=uowEgO2bjBM works only one way (can detect harp -> another instrument), but not the other way around (from another instrument -> harp), because both another instrument -> another instrument and another instrument -> harp will trigger observer pulse, rendering the signal undistinguishable. 

Hope this behavior could be fixed in 1.19 release, so it could be greatly utilized in the design of mud based clay farm. 

Yes, this issue could be categorized to the underlying issue MC-123217. 

The comment I wrote were mentioning that unlike the "Light opacity" and "Solid top" which is a property of original block itself, "instrument" is not original block's inherent property, but determined by another block (note block) and is the state of that block.

I didn't find relevant referenced issues in MC-123217 that isn't about some inherent properties of moving blocks (may be sculk sensor works the similar way with note block?), so I wrote the comment above to clarify this before categorizing this issue into MC-123217.

I've searched through the linked main ticket https://bugs.mojang.com/browse/MC-123217, and did not find a behavior related to the one in this issue. Possibly it's because this issue is not about the behavior of the moving block, but the block that interacts with the moving block (the note block).

This issue could certainly be fixed by dealing with the moving block (by attaching the information of original block/type of block to the moving block), but by considering the note block only, this issue could also be easily fixed by not updating instrument state when the block below is a moving piston block.