Discontinue of service of Flash Player on internet browsers.

Your assessment of the credible reporting sounds pretty accurate.  As usual, reports of our death are greatly exaggerated.  I would encourage anyone looking for accurate information to go find the actual public statements by the individual browser vendors for clarity on the browser roadmaps.

In my personal opinion, an unfortunate number of tech blogs generally tend to confuse what they'd like to see happen with what's actually happening in the space, and it's too common to see published speculation (and regurgitation thereof) instead of actual researched stories.  There are definitely still bright spots where people are bringing journalistic integrity to tech journalism, but like the larger journalistic landscape, it's an under-appreciated and sorely needed few doing quality reporting.

That said, there's an obvious trajectory towards making Flash content more difficult to run in the browser, and while ads and tiny content (tracking pixels, analytics, etc.) are the target today, it probably behooves you to start migrating your content towards HTML5.  Despite a huge effort to harden Flash, like the browser, it's primary job is to process untrusted, potentially malicious content, and that inherently expands the browser's attack surface.  Constraining what Flash runs to only trusted authorized content by way of click-to-play is a predictable strategy, which makes the attack surface impractical and generally uninteresting to bad guys.

There's already clear precedent in how the browser community handled the Java plug-in, and while there's a lot of great educational content built on Java still in use in higher learning today (particularly in the computer science and higher-level math arenas), it's painful and cumbersome to run, requires changing security settings, and would be a much better experience as native HTML content.

Unless you need features in Flash that aren't available in HTML and JavaScript (Flash technology is still superior for things like complex 3D games and commercial broadcast video), HTML is the optimal choice -- especially if you're building new content.

As far as Animate CC goes, it's actually a great choice for targeting either HTML5 Canvas or Flash.  Animate CC offers the same familiar workflows that Flash animators are comfortable with, but it will output directly to HTML5.  If you already have simple Flash-based animations and/or ActionScript 3 content that you want to reuse, converting them to HTML Canvas is also generally pretty easy.

Create HTML5 Canvas documents in Animate CC

For video, Adobe Media Encoder should provide an easy mechanism for converting existing .FLV video to H.264 video suitable to HTML embedding.

In short, while Flash Player is not going away tomorrow, it's certainly difficult to predict with any kind of certainty what things will look like a decade from now, especially when the decision to deprecate plug-ins lies with the individual browser vendors.  We're committed to keeping existing Flash content working to the extent possible, and while I find it unlikely that browser vendors would completely eliminate users' ability to choose to run Flash Player, it's easy to see a future where there's more friction in the experience.

Standardizing your content on HTML5 is your best bet for long-term compatibility, and for minimizing time spent on students' issues viewing course content.

Hope that helps!