I fail to see the difference between Blazor Standalone and Blazor Interactive WebAssembly .NET 8.0

My initial thought was that if I needed PWA, what was a requirement for the app, then I would need to choose Blazor Standalone.
It took me 4 weeks to implement cookie auth in the client, with and without Identity, and it would have come out of the box, if I had chosen Blazor Web App interactive WebAssembly instead.

This I do not understand:

"Blazor Web Apps support interactivity with client-side rendering (CSR) that relies on a .NET runtime built with WebAssembly that you can download with your app. When running Blazor on WebAssembly, your .NET code can access the full functionality of the browser and interop with JavaScript. Your .NET code runs in the browser's security sandbox with the protections that the sandbox provides against malicious actions on the client machine.

Blazor apps can entirely target running on WebAssembly in the browser without the involvement of a server. For a standalone Blazor WebAssembly app, assets are deployed as static files to a web server or service capable of serving static content to clients. Once downloaded, standalone Blazor WebAssembly apps can be cached and executed offline as a Progressive Web App (PWA)."

Blazor Web App interactive WebAssembly template:
Has a client and server project, then I would be able to deploy them individually ?
A user can interact with the UI ( interactive webassembly ).

Blazor Standalone:
Only a client project and I would need to create a server project myself.
Are deployed as static files, different than interactive WebAssembly files ?
A user can interact with the UI ( not interactive webassembly ? )

PWA:
From my understanding, then I should be able to convert an existing Blazor WebAssembly App in to a PWA.
Converting seem like a misleading word, because the Blazor WebAssembly would still be able to run as before the convertion, in the clients browser, but with the possibility to be downloaded to the client, so it can run fully offline.
So I would actually add PWA to the app instead of converting it ?
Can I add PWA to the client project of a Blazor Web App interactive WebAssembly ? or does it need to be a Standalone with static files ?

If Blazor Web App interactive WebAssembly supports PWA, then why would I choose Standalone over Blazor Web App ?
I guess there is a reason that I can not choose a Blazor Web App interactive WebAssembly + PWA template in VS 2022.

There is clearly something missing in my understanding of interactive vs static and maybe a lot more I miss.