Support full-URL path patterns (micro-frontends) in @effector/router-paths

[sergeysova]

Problem

atomic-router escapes :// so a full URL can be used as a route path (https://host/app/:id) — used in micro-frontend setups matching absolute links. The @effector/router-paths compiler tokenizes on /, so :// in a pattern currently breaks compilation. The rest of the MF story already works (per-MF base, shared createRouterControls, queryAdapter({ key }) for layering routers on one URL) but is not documented as a pattern.

Proposed solution

Two parts. (1) Teach the tokenizer (prepare-parser/prepare-builder) to treat :// as an opaque segment boundary instead of splitting it — full-URL patterns compile and match; pure grammar extension, existing paths unaffected. (2) Add a "Micro-frontends" docs page describing the recommended composition: one router per MF with its own base, optional shared controls, queryAdapter keyed mode for overlay routers, and full-URL patterns for absolute matching.

Alternatives considered

Pre-encoding :// in userland patterns — leaks into build() output and every Link href.

Package

@effector/router-paths