OK .. I take your point ... I am just trying to analyse the problem logically, so exploring all options.
You are correct in that Aqua has no problems with notifications to the Android phone (in fact I have never had any problems with Aqua since I bought it over a year ago).
So maybe it is at the Gear 2 end .. since it is running the Tizen operating system something is not being posted correctly. Aqua uses the same generic notification feature of the Gear Manager that all other (non-Samsung apps) use. I am not seeing the same problem with other apps (on my phone) using this generic notification procedure ... hence my "guess/suggestion" that the issue must be linked to the content and/or packaging of the notification ... most probably a character embedded in the notification that is interpreted as a control character that either causes the premature termination of the notification string or is ignored so one message merges into another. Maybe other apps don't encounter this problem because: either they don't post multiple notifications, or the notifications are much shorter, or the content of the notification does not use non-ascii characters.
So I agree, it is not the fault of Aqua - but lies in Gear Manager. So I guess I'm going to have to live with it because "yes" I have tried contacting Samsung .. but this is a totally pointless exercise
I hope the other members of this forum appreciate the quick and detailed replies you post. Keep up the good work.