@mddsharpp Hi. This is a known issue. It’s why we’ve been working to fix in the 1.0 release. It is currently available in release candidate 2 on GitHub: https://make.xwp.co/2018/11/05/amp-plugin-release-v1-0-rc2/?amp
Note that I linked you there to the AMP version of the page. Notice that it looks the same as the non-AMP version of the page: https://make.xwp.co/2018/11/05/amp-plugin-release-v1-0-rc2/ (This is running a child theme of Twenty Fifteen.)
The goal of 1.0 and the new paired/native modes is to allow you to re-use your active theme’s templates and styles in AMP, including support for category pages. The plugin includes built-in core theme support for AMP, and other themes will generally behave in AMP as if JS is disabled (since custom JS is not currently allowed in AMP). At this stage it is best geared toward site owners who have a small about of technical experience with theme/plugin development. Another example of a site that is using the new paired mode is my own, which runs a child theme of Twenty Seventeen: https://weston.ruter.net/?amp
