MAUI Blazor Browser

Make shared MAUI Blazor Hybrid UI safely accessible to a browser without turning the native application into a server or overstating what browser evidence proves.

Non-negotiable boundaries

• Preserve repository instructions, user scope, and existing architecture. Treat review or diagnosis requests as read-only unless implementation is authorized.
• Keep the native MAUI executable free of silently introduced listeners, server endpoints, server render modes, and browser-only dependencies.
• Never make a Web host reference the MAUI executable. Move shareable Razor UI and abstractions into a host-neutral RCL instead.
• Never expose production data, secrets, privileged operations, or non-loopback listeners through a temporary harness by default.
• Never install workloads, templates, packages, browsers, or tools without authorization. Use $audit-dependencies before adding or changing any package, tool, or workload.
• Never equate a rendered page or screenshot with a working interactive Blazor circuit, and never equate browser behavior with native behavior.

Read the focused references

• Read dual-host-architecture.md before selecting or changing the project topology, render modes, DI boundaries, static assets, or host-specific adapters.
• Read browser-host-safety-and-verification.md before creating or running a local browser host and before reporting browser or native evidence.

Workflow