Cross-Platform Readiness

To make scenario code portable for cross-platform deployment, audit environment variables, resources, storage, and network patterns to remove monorepo-specific assumptions, then apply fallback configurations for desktop, mobile, or cloud runtimes.

Your scenario crashes when bundled for desktop or mobile runtimes because it likely assumes Tier 1 lifecycle services, relying on sticky environment variables, hardcoded resources, or unstable storage paths unavailable outside the local stack.

For portable environment fallback patterns, you need to audit VROOLI_* and SCENARIO_* usage, then add BUNDLE_ROOT, APP_DATA_DIR, and PORT overrides with desktop and mobile detection before relying on lifecycle inputs.

To replace PostgreSQL and Redis dependencies for a portable resource strategy, swap them for SQLite and in-memory caches, document these choices in service.json, and ensure runtime swaps are intentional.

Statically compiling binaries with CGO_ENABLED=0 helps with cross-platform readiness by ensuring storage, build, and network readiness, allowing you to route mutable files through api-core/storage and accept both localhost variants.