Raw Payload
The original browser resolver remains available unchanged.
The public route now hosts a calmer shell, while the original static payload remains available under a subordinate app path.
Resolver Surface
The browser resolver is framed by the shared tool shell while the raw payload remains available at /resolver/app/.
Resolver UI
Resolve UMIDs in the browser without exposing an isolated sprint-era surface.
The resolver UI is now framed by the same shared shell used for the rest of the public tool tier. The original
static payload remains intact under /resolver/app/, while this route explains the boundary between
the standards host and the runtime resolver at myum.net.
Resolver Payload
The original resolver UI now runs inside a stable shared frame.
The internals are left intact for now. This change gives the resolver family a calmer public entry route and keeps the raw UI reachable when you need it.
Related Surfaces
The resolver family now has a clearer route map.
Use the shared-shell routes when you want context and stable framing. Use the raw payloads when you need the underlying technical surface directly.
Operations
Use the technical snapshot when you need lower-level endpoint probes.
The ops surface remains useful for resolver health checks, method probes, ETag revalidation, and quick endpoint inspection.
Runtime Boundary
The actual resolver runtime stays on myum.net.
This shell explains and frames the resolver UI; it does not collapse the standards host and the runtime host into one surface.