A good point about bare bones. It's rare for me to fly without 5-6 add-ons at least so I quickly forget what it's like flying the out-of-the-box product.
What you say about unexpected behaviour is rather what I was anticipating. I guess I was hoping for a test-harness which could "do what SimConnect does" in various scenarios without the overhead of the full UI. Without this I think I'll take a layered approach using
Lower level functions which have no regard to the machinations of SimConnect. These can be unit tested in the usual way.
A "talks to SimConnect" layer which, from what you say, will be something of an iterative process as I see how the API responds in real time.
Thanks for your input - Really useful.