Feature Request: Service Worker for true PWA install support

[TyanColte]

Summary

Homepage already has a pwa: config block in settings.yaml that generates a manifest, but there is no service worker registered. Without a service worker, Chrome on Android cannot mint a WebAPK, so "Add to Home Screen" only creates a basic browser shortcut with no app drawer entry and no standalone app wrapper.

Expected behavior

With a registered service worker (even a minimal pass-through one), Chrome treats the site as a true installable PWA. The user gets a proper install prompt, the app appears in the Android app drawer, and it opens in standalone mode with no browser chrome. The same experience as any other installed app.

Current behavior

The pwa: block in settings.yaml generates a manifest, but homepage serves no sw.js and registers no service worker. Chrome recognizes the manifest but will not offer a proper PWA install. "Add to Home Screen" falls back to a basic shortcut.

Proposed solution

Add a minimal service worker. It does not need offline caching or anything complex. A simple install/activate/fetch pass-through is enough to satisfy Chrome's installability criteria and unlock true WebAPK minting.

Something like:

self.addEventListener('install', () => self.skipWaiting());
self.addEventListener('activate', (e) => e.waitUntil(clients.claim()));
self.addEventListener('fetch', (e) => e.respondWith(fetch(e.request)));

Paired with registration in the app:

if ('serviceWorker' in navigator) {
  navigator.serviceWorker.register('/sw.js');
}

This is a small change that would make the existing pwa: config actually deliver on what it implies: a proper installable app experience.