That's a good question - and perhaps Emily can provide a more complete answer.
My take is that the vendors involved in the overall project (1) don't want to bloat the overall specification and (2) don't agree that those APIs/sub-specifications are essential enough to be part of the overall specification. MP Context Propagation probably should be in the overall spec group - but instead it is transitioning to the Jakarta community to be part of Jakarta Concurrency. I think this makes sense - and ideally, Jakarta Concurrency will be part of the overall MP spec. So unless things change, I do foresee MP Context Propagation making it into the overall spec - just in a roundabout way.
As for Reactive Messaging (and the Reactive Stream Operators project that it depends on), I don't know why it's not part of the overall spec - but I suspect that the vendors involved see Reactive Messaging as somewhat niche and want to see more adoption before including it. I think that that may also be the case for MP GraphQL and LRA.
If you'd like to voice your opinion on what should be included in the overall spec - or offer feedback on any of the specs, you can join the mailing list (Google Group) at:
https://groups.google.com/g/microprofile