7 Commits

Include renames

Author	SHA1	Message	Date
Raven Scott	e6658d4421	fix(pwa): resolve proxy connection reset and manifest same-origin warnings ... Fix "Proxy error: connection reset by peer" caused by dashboard-server.js looking for files in native-host/ instead of extension/dashboard/. Remove the devBasePath parameter and resolve DEV_DASHBOARD_DIR directly from __dirname so dev and distribution mode both find the correct files. Fix all manifest warnings (start_url/id/scope/protocol_handlers ignored) by reverting manifest.webmanifest to relative/extension-origin URLs for the chrome-extension:// context, and having dashboard-server.js dynamically generate a manifest at /manifest.webmanifest with absolute https://my.dash.board/ URLs — satisfying Chrome's same-origin requirement for PWA installability. Also serve extension icons at https://my.dash.board/icons/<file> with correct bundle key mapping, and embed them in the distributable binary via build-distributable.js.	2026-03-01 03:10:11 -05:00
Raven Scott	a838c3a345	feat(pwa): experimental — add my.dash.board virtual host for secure PWA install ... Serve the dashboard over a local HTTPS virtual host (my.dash.board) so Chrome treats it as a secure origin and shows the PWA install prompt. - Add native-host/dashboard-server.js: bare-http1 static file server backed by bare-bundle assets in distribution mode, disk fallback in dev - Add setLocalVirtualHost() to virtual-hosts.js; type:local entries are protected from removal and filtered out of saveState persistence - Export setLocalVirtualHost from holesail-manager/index.js - Start dashboard server in startup.js after proxies are ready and register my.dash.board as a local virtual host - Stop dashboard server in message-router.js cleanup() - Update manifest.webmanifest: start_url, id, scope → https://my.dash.board/ - Embed all extension/dashboard/ files as bare-bundle assets in build-distributable.js patchBundle() — no installer copy step needed - Hide checkbox, hs:// URL, Reconnect, and Remove controls for built-in my.dash.board row in the virtual hosts table UI	2026-03-01 02:58:52 -05:00
Raven Scott	0ec696c00d	feat(pwa): add service worker and scope for full PWA installability ... Add a minimal sw.js with an empty fetch handler — required by Chrome for the PWA install prompt to appear. Register it at the bottom of dashboard.html with a silent catch. Add "scope": "." to the manifest. Register sw.js in web_accessible_resources so Chrome can fetch it from the extension origin.	2026-03-01 02:16:37 -05:00
Raven Scott	96e40d1b96	fix(pwa): resolve manifest warnings for cleaner PWA install experience ... - Fix icon purpose from "any maskable" to "any" to avoid incorrect padding on some platforms - Add explicit id field matching start_url to stabilise the App ID - Add display_override with window-controls-overlay for native title bar - Register web+holesail:// protocol handler so installed app can be launched directly from custom protocol links	2026-03-01 01:56:30 -05:00
Raven Scott	a2692b3760	feat(pwa): add screenshots to manifest for richer PWA install UI ... Add wide (1024x515) and narrow (390x844) screenshots to the web app manifest so Chrome displays the richer install UI with a preview on both desktop and mobile. Register screenshots directory in web_accessible_resources so Chrome can fetch the images from the extension origin.	2026-03-01 01:49:26 -05:00
Raven Scott	ac7df32be7	feat(pwa): add proper icon sizes and update all icons from new 512px source ... Replace all extension icons (16, 32, 48, 128, 192, 512) with versions derived from the new 512x512 brand icon for consistency. Add 192x192 and 512x512 entries to manifest.webmanifest — Chrome requires both sizes to show the "Install page as app" option in the browser menu. Mark the 512px icon as maskable for OS launcher compatibility.	2026-03-01 01:46:32 -05:00
Raven Scott	e391d82316	feat(pwa): add PWA install support and update installation docs ... Add manifest.webmanifest to the dashboard so Chrome can install it as a standalone app via the browser menu. Register the manifest in web_accessible_resources and link it from dashboard.html. Add a dedicated PWA install section to docs/INSTALLATION.md covering install steps, uninstall, and the requirement that the extension remains installed.	2026-03-01 01:36:37 -05:00