feat(maestro): export replay flows that switch apps

[PLASMA-FR]

Summary

replay export now preserves app switches in recorded flows:

open com.example.shop
open com.example.auth
open com.example.shop

Each launch carries its own launchApp.appId; the first app remains the flow default. This completes the existing local export workflow from #751 using already-supported Maestro syntax. Relaunch options and deep links retain their authored targets and order.

Eight files (+94/−32): exporter, behavioral regressions, CLI help, user docs, and changelog.

Validation

Tested commit: 865ed651a5b3b20c79b69b1ade0b2d236c905b3b (Linux arm64, Node 24.13.1, pnpm 11.17.0).

• Three app-switch regressions failed on unchanged main (64867883) and pass with this change.
• pnpm exec vitest run packages/maestro/src/internal/__tests__/export-navigation.test.ts packages/maestro/src/internal/__tests__/export-label-projection.test.ts src/cli/commands/__tests__/replay-maestro-export.test.ts: 19 passed.
• pnpm maestro:conformance: 62 passed.
• pnpm check:affected --run: passed, including build, formatting, lint, types, layering, Fallow, and 2,193 related tests across 294 files.
• Built CLI stdout, JSON, --out, help, and unsupported-action refusal passed with an unreachable daemon URL.

Initial validation exposed missing host zip/unzip and a startup timeout. Archive tools are now provisioned; the final gate passed with four workers and unchanged test limits. CI is pending; full Coverage and Integration Tests remain GitHub-authoritative.

[thymikee]

Code review is clean at 865ed65. Explicit launchApp.appId values preserve app switches, relaunch options and deep-link order through the existing runtime, and the regressions cover the previous rejection. Checks pass and there are no conflicts; ready for human review.