Inserting cues

My idea

I decided not to explain in detail what cues are in parts/in the full score and what I (and not only) would like to see in MuseScore Studio, because I think @oktophonie knows the rules of their notation perfectly well. I also take into account his comment on this matter.
Personally, I would like to mention some details on my own that will help the performer better navigate through these cues.

1. The ability for the user to quickly specify a cue in the part by highlighting an instrument in the full score and selecting the appropriate action.
2. Have various parameters for inserting cues (with/without articulation/dynamics, on a separate cue-sized stave, etc.), including incomplete and tied ones, as well as inserting several cues simultaneously in one (with automatic signature of the corresponding instruments).
3. Automatic continuation of the numbering of rests in the event that the cue is long and is notated until the player enters. See the example:
   
4. Cues playing the role of hints in the parts should not be displayed in the full score, but cues indicating such things as "Play the cue in the absence of…" or "Play at the conductor’s discretion", etc. can be noted in the full score.
5. Notation of cues in the correct clef corresponding to the part (if necessary, automatic addition of such inscriptions as "8va bassa/alta", "col 8va bassa/alta", etc.)

Problem to be solved

Currently, there is no cues notation system at all in MuseScore Studio. To add a cue to the part, you need to perform quite a lot of actions. In this case, the cue will also be displayed in the full score.
Recently, I wrote lines in a percussion part, where there is one single-line stave. It took a lot of time and patience to do this, because there was only one percussion part in the score, and the cues had to be taken from instruments with a definite pitch.

Prior art

Sibelius has a function like "paste as cue". This is at least something than nothing at all.

Checklist

• ✅ This request follows the guidelines for reporting issues
• ✅ I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

The issue names no files, tests, or entry points; start by reviewing the existing part and full-score cue workflows and the prior-art discussion linked in the issue. Done criteria are not limited to a single change: the scope must be agreed for cue insertion, parameters, rest numbering, clefs, and part/full-score visibility before implementation can be validated.