Huge +1 on this proposal.
I’ve encountered the exact same problem when using C++ interop in one of my cross-platform Swift packages, and even reported it separately. From my experience, this looks like a bug in SwiftPM’s current handling of the swift/bridging header search path.
For reference: