Break up Mobile and Desktop

Right nwo we're relying on a LOT of responsive styles to hide/change various components between mobile and desktop. While this is good, the idea that our web app is a "good mobile app" is very untrue. Additionally this approach makes things fairly brittle as well as bloated for both mobile and web (we have to render extra components).

So instead, lets do the following:

• Keep web as the "web" experience. It should be responsive, but it should focus on desktop.
• Build a new "mobile" app - a new Vite frontend that's simple a react PWA/SPA. Git history has prior art but not really improtant.

We can move the components into shared/design to make it easy to share things that are overlapping. This will allow us to do something like m.peated.app (which we'll auto redirect to on phone form-factors), and remove the overly complicated flows we have now.

It also means the web app can move away from the toolbar-experience and be focused on browsing, or basically not exist for all I care (as the mobile experience really should be the pure-app experience).

p.s. This is an alternative plan to building a full native-app, which maybe we want to do at some point.

Start by reviewing the existing web app and the components proposed for moving into shared/design. Define the boundaries of the new Vite React mobile app, the desktop web experience, and phone-form-factor redirection; done means the two experiences are separated without relying on the current responsive component flows.