Thank you Beth Romero. I figured this out after I posted. I guess I would ask that this be documented somewhere. The old app was updated to say Mature but no reason was given and there wasn't a link to the new app. Its not clear to me why this couldn't be a seamless update to the same configurable app id since it actually isn't a new template. Its confusing because unlike normal app deprecations, the template isn't really being deprecated, its the configuration set up. As far as I know it wasn't documented in the usual list of deprecated apps. As you noted, the launch blog post for the template was silently updated as well with no notification to users that a change was made.
As a configurable app template user, its unclear how I am supposed to know that this change was made, where the new template is at, how to migrate the existing one, especially if the AGO org group hasn't been updated.
As an AGO admin, its unclear how I am supposed to know when a configurable app was marked mature, why it was marked mature, what the recommended migration route is, and when and how frequently I should be refreshing the "share the Esri default configurable apps with group" setting.
Thanks
Josh
