ASC 2.0 Compiler bug -- still biting us

My team is still impacted greatly by a lingering ASC 2.0 compiler bug.  This is a bug that unpredictably results in build artifacts that throw Type Coercion errors at runtime.  This issue affects both Flash Player and iOS targets.

Bug 3562040 was  opened almost three years ago on this, as well as the related thread here: Type Coercion failures with MovieClips in ASC 2.0  And this issue was reportedly a high priority issue 5 months ago, but I have yet to see any note about it in the AIR 19, 20, or 21-beta release notes since: What happened to this known issue in AIR 18? Was it fixed? (ASC 2.0, Type Coercion: 3578605)‌  Is there any progress to report, or an updated timeframe in which we can expect a fix?  Is there any way we can help the Flash/AIR team get to the bottom of this?

I don't think I can over-stress how impactful this issue is to our development cycle.  It affects our productivity, it affects team morale.  And I would challenge anyone to feel good about choosing a technology that is dependent on a closed-source SDK when critical regressions can be unpredictably introduced into your product by its compiler, independent from any change to source.  And especially when the issue goes unaddressed for years.  I don't see how new features in the runtime can be prioritized when issues like this linger.  Can we please get attention on this?

Thank you,

Russell