Flex and AIR compatibilities situation

Having some trouble with an app that was compiled with Flex SDK 3.2.0.3958 meant to be deployed with AIR 1.5.3, and failing to work in an upgraded AIR (2.7-3.0) environment. This app is part of a larger, shippable distribution being sold to clients throughout the world. When the application is invoked in the 1.5.3 environment everything works as expected. But, when it is invoked in an upgraded environment (2.7-3.0) the screen momentarily flashes (as though it were launching full-screen, as it should be) and then the application dies. This behavior is present on both OSX and Windows. This AIR application is built via Maven using the flex-mojos plugin and is a critical "cog" in our product. We are unable to duplicate this same behavior when the main SWF is built within Flash Builder 4.0.1 (with the 3.2 compiler settings) on a local development machine. That is to say, if we replace the automated SWF that is deployed by AIR, with the one that is built in the IDE, the app appears to work.

First question is how do the Flex SDK and AIR runtime versions correspond, and if Adobe has released an official document that maps the two? My team and I have been unsuccessful in finding this information by scouring Adobe's site and using various search engines. Would love to have a compatibility matrix. So, here is what we've been able to piece together based on the add-ons zip accompanying (most of) the SDK downloads and the corresponding "AIR SDK Readme" file (when present, since it isn't in the 4.x series):

3.2.0.3958  -> AIR 1.5.3.9130

3.4.0.9271    -> AIR 1.5.3.9130

3.5.0.12683  -> AIR 1.5.3.9130

3.6.0.16995  -> (AIR 1.5.3.9130?, no add-ons listed)

4.0.0.14159  -> ? (add-ons zip doesn't contain the readme present in the 3.x series)

4.1.0.16076  -> ? (add-ons zip doesn't contain the readme present in the 3.x series)

4.5.0.20967  -> AIR 2.6

4.5.1.21328  -> AIR 2.6

4.6               -> AIR 3?

Second question is, are there known incompatibilities between apps working on 1.5.3 and breaking on 2.7 & 3.0?

Finally, when assessing our scenario and considering the difference of behavior in both the IDE-built (works) SWF and the automated one (broken), we are depending on the artifacts as served up by the Maven repo at https://repository.sonatype.org/content/groups/flexgroup/ . This is potentially a failure point if they have mismanaged/mismatched the jar versions, so I'll be pursuing additional input from their list too as we try to find the difference in the builds.

All that being said, any suggestions or insight on the matter would be most helpful.

Thanks in advance,

-Russ-