That would meet the true definition of a PWA in my mind. Ideally, a PWA could utilize everything the platform has to offer by running as a native app, but can also run in the browser for an install-free experience.
"What's happiness?" on the other hand is subjective. You could describe things that make you happy, but it wouldn't make sense to point to a banana and say "That's happiness." And if you ask "Am I happy?" the answer probably isn't boolean.
"What's a PWA?" seems to fall into the latter category. If so, then we're treading into philosophy territory, which has claimed countless victims over millennia. You can spend a lifetime trying to define love, but at the end of it, you probably won't produce work that can be built on and extended, the way scientific papers can.
It's notoriously difficult to pin down philosophical concepts into discrete buckets of meaning. We have to operate at the resolution of words. They break if you push them too far.
I think it's important to distinguish these two domains. If we can't effortlessly point to dozens of examples of PWAs, it might be better to reject the notion that PWAs can be defined at all.
And I wouldn't say the non-technical folks are idiots! They know a lot of stuff I don't, you just need to nail the overlap in what we both know. And given how difficult it is to explain the Service Worker API to even a skilled developer, best to take a pass.