Chords symbols shift layout on when editing a system above

[Tadaboody]

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

1. Create a system with tempo, text and chord symbols
2. Edit a system above
3. chord symbols jump over other items

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/e2e7664f-4e02-4a12-a3c9-0b1398dde8cd

In which versions of MuseScore Studio is this issue present?

OS: macOS Sequoia (15.5), Arch.: arm64, MuseScore Studio version (64-bit): 4.6.4-253351238, revision: github-musescore-musescore-8af129b

Regression

I was unable to check

Operating system

15.5 (24F74)

Additional context

I'm willing and eager to work on a fix with some guidance :)
sorry if there are similar issues, I couldn't find one with the exact case

Checklist

• [x] This report follows the guidelines for reporting bugs and issues
• [x] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• [x] I have attached all requested files and information to this report
• [x] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[MarcSabatella]

This is probably the same as #31343 , but this issue shows the problem is more more widespread and not limited to just voltas.

Luckily, it remains just a temporary visual glitch that fixes itself on the next layout of the affected system. But still an annoying one.

[Tadaboody]

Luckily, it remains just a temporary visual glitch that fixes itself on the next layout of the affected system. But still an annoying one.

Sadly I've already exported scores with the visual glitch intact :/

[MarcSabatella]

If you simply reopen the score you'll find the glitch has resolved itself and you can re-export it.

[Redondoguy]

See #31343 video. It shows a chain reaction of moving chords in system 2 moves chord symbols in system 4 and then fixing 4 moves those in system 6. The exported pdf is flawed if all not fixed before exporting. The user has a high probability of not seeing all these and will publish the flawed pdf. The only safe solution is to save file > quit > reopen > export pdf. I'm sure most users would find this cumbersome IMO this is a top priority issue to get fixed.