feat: NativeScript support

[NathanWalker]

NativeScript support: Core, Octane, React, Vue, Svelte, Solid and Angular apps

screenmap now maps NativeScript apps, whichever framework drives the views, and runs them through the same capture, pack, diff and viewer pipeline as an Expo app. Five commits, each self-contained:

1. Read NativeScript apps — a nativescript route provider with one flavour per framework.
   • Core: <Page> XML files and Frame.navigate({ moduleName }) / showModal().
   • Octane, React, Vue, Svelte, Solid: no route table, so a screen is a component the framework mounts as a root, pushes, presents as a modal, hosts in a <frame> tab, or registers in a solid-navigation <Route> table. One shared engine, one row of spellings per flavour.
   • No flavour has a linking config: the app registers a URL scheme in App_Resources and maps URLs onto navigation in its own code. Every route starts navigation-only and routes.links in .screenmap/config.json names the ones a deep link opens. Scheme, app id and name are read from nativescript.config.ts, Info.plist (xcconfig variables resolved) and AndroidManifest.xml.
   • Angular: follows provideNativeScriptRouter(routes) into every loadChildren module; reads named outlets, redirectTo aliases, enum-valued paths, barrel re-exports; a route with children is a layout (tabs when its children sit in several named outlets); edges from navigate([...]), navigateByUrl() and nsRouterLink, with relativeTo honoured.
2. Run a NativeScript build — the JS ships inside the .app/.apk, so the session installs and launches it and that is the whole boot. Builds are found under platforms/. An app with no URL scheme has its root captured by launching. A ns debug build under @nativescript/vite (a stub that imports core from the dev server) is refused with the dev-server origin and the ns build command, instead of silently capturing the simulator home screen.
3. Viewer fix — flowResolution built an open_url matcher for every node and split a null urlPath; any react-navigation map with a screen outside its linking config would have crashed the same way.

Validated against real apps

App	Framework	Static parse	Runtime (iPhone 17 Pro simulator)
ns-octane	Octane, Vite	root + settings sheet (modal), drawer hint	root captured by launch (no URL scheme)
ns-apple-music/ns-angular	Angular, Vite	6 routes, listen-now as the landing /	root captured by launch
ns-apple-music/ns-vue	Vue, Vite	9 routes: Home + 5 tab screens + album + 2 modals	root captured by launch
ns-apple-music/ns-solid	Solid, Vite	8 routes, <Route> table, router shell read as a layout	app halts in a plain ns build (app-side, see below)
HeyKiddo Talk	Angular, webpack	54 routes, 9 layouts, 61 edges, 1 unresolved (a commented-out route)	20 of 20 deep-linked screens captured, logged in

Detection scores 0.95 on all five with nothing else above 0.10. Nine fixtures pin the graphs (node fixtures/run-tests.mjs).

Each image below is the map viewer showing the packed .scrmap from one run (screenmap-ci shot), deterministic lane only, no agent: captured screens are real screenshots, the rest are navigation-only and wait for flows or the agent.

Octane — the chat root and the settings sheet it presents as a second Octane root.

Angular — five named-outlet tabs read as Tabs, the album screen reached from four of them.

Vue — the same app in Vue: tab screens hosted in <Frame>s under Home, $navigateTo and $showModal edges.

Solid — solid-navigation's <Route> table and navigate('Album') by name. The black root is the app itself: a plain ns build ios of it halts at launch with Solid's REACTIVITY_HALTED thrown from solid-navigation, so it only runs under its HMR session.

HeyKiddo Talk (Angular) — 54 screens, 20 reached by deep link through the app's own com.heykiddo.talk:// handler.

For reviewers

• CI never builds, so a NativeScript project passes a prebuilt .app/.apk as app_path; the EAS lane and expo_token do not apply.
• routes.provider pins the provider when detection is wrong; routes.links is the deep-link overlay. Both are in the config table in the README.
• No existing fixture snapshot changed; the expo-router and react-navigation graphs are unaffected; purely additive feature