I have never experienced this either, and not sure what is happening. As your project is complex, the steps of:
- I copy one of the introductions and paste into the 1st track.
- Delete the fourth track.
- Listen, edit, save.
should not delete anything. SONAR doesn't delete any files on you, so they should all still be on disk. Is that "save" as a bundle file or a cwp using per project audio folders?
Just to clarify, is the introduction clip still visible, just "empty"? If so, you can hit Shift-K and re-associate that clip to its proper wave file. As you have many clips (being saved as their own wav files), the clip names are important to keep track of to do this, but they should not be gone.
In your case, I would suggest "per project audio folders" rather than bundle files. Then you can also verify using Windows Explorer in the audio folder that you are seeing the moved introduction is still there (renaming the clip before the save should verify that a new file is created). If not, that is a bug.
As far as "project cleanup," the best method to strip out unused wav files is to do a "Save As" on the project when finished, and create a new project folder when doing so. This will save only the cwp and associated wav files to the new folder created, but should leave everything in the original folder.
[this is really more of an aside, and not directly related] Bundles do have the advantage of consolidating audio to an area of a disk, but otherwise are best used to collaborate on projects IMO. A magnetic disk (HDD) will write to its first available space, so saving each clip as a wav can potentially scatter them about and induce latency from seek times. From a "disk read" perspective, I tend to bounce all clips on a track to a single clip (even with silence), since it can ease HDD seek times. For SSDs, this does not apply.
Bundles also induced unnecessary "packing/unpacking" overhead, so unless collaborating or consolidating files, this is just adds to save/load times.