Summary

Introduce per-app PWA branding and icons across server and client:

• Server endpoints for app icons and manifest access with appropriate public scope
• Client support for maskable icons, editor and ApplicationV2 updates
• Documentation for PWA icons/favicons in the app editor

Motivation

• Brand-aware PWA install with proper icons (including maskable) and metadata per application
• Improved favicon and manifest handling for the editor and installed apps
• Developer guidance for configuring PWA assets

Changes

Server

• Add per-app icon controller and endpoints
• Refactor ApplicationController to enhance manifest/title handling
• Adjust security to allow public access to PWA resources as needed
• Add local-dev config
• Update tests for new endpoints and logic

Client

• Support per-app icon handling and conversion utilities
• Improve editor view and ApplicationV2 to surface correct branding/icons
• Add maskable icons and related manifest enhancements

Docs

• Add guide: PWA icons and favicons for the app editor

Testing

• Verified client pages render correct icons in editor and runtime
• Confirmed maskable icons and manifest fields are present and valid
• Exercised server endpoints for app icons and manifest with expected responses
• Updated/ran related server tests

Backward compatibility

• Additive; apps without custom icons fall back to defaults

Security

• Manifest/icon endpoints intentionally public; other APIs unchanged

Commits (organized)

• feat(pwa-server): per-app icon endpoints, manifest security scope, local-dev config; refactor ApplicationController; tests updated
• feat(pwa-client): per-app PWA icon handling, maskable icons, editor display, ApplicationV2 updates; add icon conversion utils
• docs(pwa): add PWA icons and favicons guide for app editor