That did the trick, but I've run into a new issue. I'm building a simple demo to let you paste in content and then summarize using the "old" more indepth model and the new speedy one.
As part of my demo, I ran into the issue of needing a user gesture when availability is downloadable/downloading. I added a check for that, but didn't pass the options in. So that's my fault, and in a real project I don't think you would do both.
But as a followup - if I I modify my availability() call to check for performance:speed, it would NOT correctly handle a case where the *default* Summarizer model is downloaded - and I'd need to handle _both_ cases... correct?