@lotics/cli 0.88.0 → 0.88.1

package/dist/starter_template.js

@@ -1,753 +0,0 @@
-/**
- * Starter template for `lotics app create`.
- *
- * The CLI scaffolds these files into the user's target directory, then runs
- * `npm install` + `npm run build` + `lotics app deploy` to populate v1.
- *
- * Embedded as string literals here (rather than packaged as files alongside
- * the CLI) so the CLI binary is self-contained and the starter survives
- * `npm publish` cleanly. Updates to the starter ship in CLI releases.
- *
- * Conventions (locked decisions):
- *   - Vite + React + TypeScript (strict mode).
- *   - Entry: src/App.tsx with `export default`. main.tsx wires
- *     `mount(<LoticsLocaleProvider locale={vi}><PortalHost><App/></PortalHost></LoticsLocaleProvider>)` —
- *     LoticsLocaleProvider sets the kit's strings to Vietnamese (Lotics apps are
- *     Vietnamese; swap to `en` for English); PortalHost is the render target
- *     @lotics/ui overlays (Popover/Tooltip/Dialog) need — and imports
- *     @lotics/ui/index.css (base style reset) + @lotics/ui/fonts.css
- *     (path-independent Inter @font-face bundle — Text renders unstyled without it).
- *   - Vite default `base: "/"` so emitted asset URLs are absolute; the render
- *     endpoint rewrites root-relative paths to `/v1/apps/{id}/asset/...`.
- *     Don't switch to `base: "./"` without updating `rewriteAssetPaths`.
- *   - react-native aliased to react-native-web so @lotics/ui's RN primitives
- *     render in a pure-web environment. `.web.tsx` is prioritized in the
- *     resolve.extensions list.
- *   - @lotics/app-sdk + @lotics/ui peer-supplied; user installs both via npm.
- *   - oxlint + vitest + tsc out of the box, plus a GitHub Actions CI
- *     workflow that runs all three on every PR.
- */
-/**
- * Pin defaults for `@lotics/ui` and `@lotics/app-sdk` in the scaffolded
- * package.json. Used when `lotics app create` can't resolve the latest
- * versions from npm (no network, registry blip) — keeps `app create`
- * working offline at the cost of a stale starter pin.
- *
- * Bump these in tandem with new releases of either package. Production
- * scaffolds resolve the live version via `fetchLatestNpmVersion` and only
- * fall back here when the lookup fails.
- */
-export const STARTER_FALLBACK_UI_VERSION = "6.1.0";
-// Must be ≥ the release that added `getAppBinding` (0.51.0, used by package
-// projects' generated .lotics/app_fields.ts) — and note ^0.x caret ranges never
-// cross a minor, so a stale floor here permanently pins scaffolds below the
-// APIs the generated code imports.
-export const STARTER_FALLBACK_SDK_VERSION = "0.51.0";
-/**
- * react-native pin for scaffolded apps. Matches the monorepo frontend's pin so
- * an app deep-typechecks `@lotics/ui`'s `.tsx` source against the SAME RN types
- * the package is developed and CI'd against. A mismatch surfaces RN-version-
- * sensitive type errors (e.g. `StyleSheet.absoluteFill`, which `frontend/` CI
- * never sees because `packages/ui` is only typechecked through `frontend/`).
- * RN is aliased to react-native-web at runtime, so this pin is effectively
- * types-only.
- */
-export const STARTER_REACT_NATIVE_VERSION = "0.85.3";
-export function buildStarterTemplate(args) {
-    const uiVersion = args.ui_version ?? `^${STARTER_FALLBACK_UI_VERSION}`;
-    const sdkVersion = args.sdk_version ?? `^${STARTER_FALLBACK_SDK_VERSION}`;
-    const sanitizedPkgName = args.app_name
-        .toLowerCase()
-        .replace(/[^a-z0-9-]/g, "-")
-        .replace(/-+/g, "-")
-        .replace(/^-|-$/g, "")
-        .slice(0, 64) || "lotics-app";
-    return [
-        {
-            path: "package.json",
-            content: JSON.stringify({
-                name: sanitizedPkgName,
-                version: "0.0.1",
-                private: true,
-                type: "module",
-                scripts: {
-                    dev: "vite",
-                    build: "vite build",
-                    preview: "vite preview",
-                    typecheck: "tsc --noEmit",
-                    // Scope to src/ — oxlint's default scan walks node_modules too.
-                    lint: "oxlint src",
-                    test: "vitest run",
-                },
-                dependencies: {
-                    "@lotics/app-sdk": sdkVersion,
-                    // The FilePreview engines (pdfjs-dist / @lotics/docx / @lotics/xlsx) are
-                    // NOT listed here: they ship as @lotics/ui dependencies (7.14.0+), so
-                    // every app gets them transitively — one version source, no skew. An app
-                    // that IMPORTS @lotics/docx or @lotics/xlsx directly (its own doc/excel
-                    // builders) declares its own dependency then.
-                    "@lotics/ui": uiVersion,
-                    "@react-native-picker/picker": "^2.7.0",
-                    "expo-image": "~3.0.9",
-                    "lucide-react": "^0.562.0",
-                    "lucide-react-native": "^0.562.0",
-                    react: "^19.0.0",
-                    "react-dom": "^19.0.0",
-                    "react-native": STARTER_REACT_NATIVE_VERSION,
-                    "react-native-svg": "^15.0.0",
-                    "react-native-web": "^0.21.0",
-                    // In-app routing for the scaffolded list→detail example. The app owns
-                    // its routing; the SDK's `isEmbedded()` picks memory vs browser history.
-                    "react-router-dom": "^7.0.0",
-                },
-                devDependencies: {
-                    "@testing-library/react": "^16.1.0",
-                    "@types/react": "^19.0.0",
-                    "@types/react-dom": "^19.0.0",
-                    "@vitejs/plugin-react": "^4.3.0",
-                    jsdom: "^25.0.0",
-                    oxlint: "^0.13.0",
-                    // Track the platform's TS major so `lotics app workflow check` (which runs
-                    // the app's OWN typescript) gives the same verdict the server does at set-time.
-                    typescript: "~6.0.3",
-                    vite: "^5.4.0",
-                    vitest: "^2.1.0",
-                },
-                lotics: {
-                    app_id: args.app_id,
-                    workspace_id: args.workspace_id,
-                    current_version_id: null,
-                    version_number: null,
-                },
-            }, null, 2) + "\n",
-        },
-        {
-            path: "tsconfig.json",
-            content: JSON.stringify({
-                compilerOptions: {
-                    target: "ES2022",
-                    useDefineForClassFields: true,
-                    lib: ["ES2022", "DOM", "DOM.Iterable"],
-                    module: "ESNext",
-                    skipLibCheck: true,
-                    moduleResolution: "Bundler",
-                    allowImportingTsExtensions: true,
-                    resolveJsonModule: true,
-                    isolatedModules: true,
-                    noEmit: true,
-                    jsx: "react-jsx",
-                    strict: true,
-                    noFallthroughCasesInSwitch: true,
-                },
-                // Restrict tsc to the project's own sources. tsgo follows
-                // transitive imports into node_modules — strict rules
-                // (noUnusedLocals etc.) would fire on @lotics/ui's source.
-                // `.lotics/**/*` (not bare `.lotics`): TypeScript's include glob walk
-                // SKIPS dot-directories, so a bare `.lotics` silently loads zero of the
-                // generated `.d.ts` augmentations and typed useWorkflow/useQuery/useAgentRun
-                // fall to `unknown`. The explicit glob makes the dot-dir the non-wildcard
-                // base, which IS read. (GAP-38.)
-                include: ["src", ".lotics/**/*"],
-                // src/workflows/<alias>.ts bodies run on the server (workflow globals:
-                // trigger / runtime / tool calls), and each pulls its own per-alias
-                // ambient globals under `.lotics/workflows/`. BOTH are excluded from
-                // the main typecheck: the bodies would apply the app's DOM lib (the
-                // server doesn't), and the per-alias `.globals.d.ts` files each declare
-                // their OWN ambient `trigger` — loading several into one program
-                // collides those declarations and reports false errors. Type-check the
-                // bodies with `lotics app workflow check` instead — it builds ONE
-                // isolated program per alias (mirroring the server's set-time verify),
-                // so the ambient `trigger` is unambiguous. The server stays the single
-                // verifier on `lotics app workflow set`.
-                exclude: ["node_modules", "src/workflows", ".lotics/workflows"],
-            }, null, 2) + "\n",
-        },
-        {
-            path: "vite.config.ts",
-            content: `/// <reference types="vitest" />
-import { defineConfig } from "vite";
-import react from "@vitejs/plugin-react";
-
-// Vite default base (/) emits absolute asset URLs in index.html. Lotics's
-// render endpoint rewrites those to /v1/apps/{id}/asset/... so the bundle
-// loads via the platform's asset proxy. Don't change \`base\` unless you
-// also adjust the rewrite logic in backend/api/apps.ts:rewriteAssetPaths.
-//
-// react-native → react-native-web alias lets @lotics/ui's RN primitives
-// (View, Text, Pressable, StyleSheet, etc.) render in a pure-web environment.
-// .web.tsx is prioritized in resolve.extensions so per-target variants
-// (avatar.web.tsx, wave_avatar.web.tsx) win over the native .tsx file.
-//
-// @lotics/ui/icon.tsx imports from \`lucide-react-native/dist/esm/icons/<name>\`
-// — deep paths that lucide-react-native's package \`exports\` map blocks under
-// Vite's strict resolution. lucide-react has the same per-icon files with no
-// exports map, so we alias the deep path to use it. Web rendering of <svg>
-// is identical to RN-SVG when running under RN-Web.
-export default defineConfig({
-  plugins: [react()],
-  // RN libraries reference globals Metro injects but Vite does not — undefined
-  // ⇒ the bundle throws. \`__DEV__\` (react-native-web, @react-native-picker's
-  // UnimplementedView): throws at load, blank iframe. \`global\` (rn-web
-  // Animated's \`global.cancelAnimationFrame\`): throws when a spring animation is
-  // interrupted/torn down — e.g. toggling @lotics/ui's Switch. rollup hits it;
-  // the dev esbuild path masks it, so it only surfaces in the deployed app.
-  // rn-web only reads \`global.x\` as a free var, so mapping it to \`globalThis\`
-  // is safe. Define both so dev and the deployed build behave identically.
-  define: { __DEV__: "false", global: "globalThis" },
-  resolve: {
-    alias: [
-      {
-        find: /^lucide-react-native\\/dist\\/esm\\/icons\\/(.+)$/,
-        replacement: "lucide-react/dist/esm/icons/$1",
-      },
-      { find: "react-native", replacement: "react-native-web" },
-    ],
-    // \`.web.js\` resolves the web build of RN packages that ship \`X.js\` (native)
-    // beside \`X.web.js\` (web) — e.g. @react-native-picker/picker, whose compiled
-    // \`Picker.web.js\` renders a real <select>. Without it the extensionless
-    // \`require("./Picker")\` picks native \`Picker.js\` and the standard Picker
-    // renders nothing on web.
-    extensions: [".web.tsx", ".web.ts", ".web.js", ".tsx", ".ts", ".jsx", ".js"],
-    // @lotics/ui ships source and is consumed across many subpath entries
-    // (./card, ./metric, ./use_screen_size, …). Without dedupe, Vite can
-    // pre-bundle a subpath into its own chunk with a second React copy — a
-    // hook called from there hits a null dispatcher ("Invalid hook call").
-    // Pin React (and RN-Web) to a single instance shared by every chunk.
-    dedupe: ["react", "react-dom", "react-native-web"],
-  },
-  optimizeDeps: {
-    // \`react-native-svg\` (used by @lotics/ui's svg charts — PieChart, LineChart,
-    // Sparkline, RingGauge) ships a named-export entry Vite's dev optimizer won't
-    // resolve unbundled ("does not provide an export named 'parse'"), blanking the
-    // iframe the moment one of those charts renders. Pre-bundling it fixes the
-    // interop. Production build (rollup) resolves it without this — dev-only.
-    //
-    // react-native-web itself is force-prebundled (folds its core CJS deps like
-    // @react-native/normalize-colors into one interop'd chunk), and the deep
-    // subpaths it reaches via *default* imports (e.g. @react-native-picker's web
-    // <select> build) are each pre-bundled into an ESM shim — Vite's dev optimizer
-    // otherwise serves them without a synthesized default export ("does not
-    // provide an export named 'default'"), blanking the iframe. (Production/rollup
-    // resolves the interop already, so this is dev-only.)
-    //
-    // \`react-markdown\` (@lotics/ui's Markdown renderer, reached by AgentRun and
-    // any markdown surface) pulls a transitive CJS dep, \`style-to-js\`, whose
-    // default export the dev optimizer won't synthesize unbundled ("does not
-    // provide an export named 'default'") — blanking the iframe the moment a
-    // markdown component mounts. Pre-bundling react-markdown folds the whole
-    // subtree (incl. style-to-js) into one interop'd chunk. It is a regular dep
-    // of @lotics/ui (hoisted), so it needs no package.json entry here. (The GFM
-    // plugin @lotics/ui composes is pure ESM — no CJS interop to force.)
-    include: [
-      "react-native-svg",
-      "react-markdown",
-      "react-native-web", "@react-native/normalize-colors",
-      "inline-style-prefixer/lib/createPrefixer",
-      "inline-style-prefixer/lib/plugins/crossFade",
-      "inline-style-prefixer/lib/plugins/imageSet",
-      "inline-style-prefixer/lib/plugins/logical",
-      "inline-style-prefixer/lib/plugins/position",
-      "inline-style-prefixer/lib/plugins/sizing",
-      "inline-style-prefixer/lib/plugins/transition",
-      "postcss-value-parser", "fbjs/lib/invariant", "fbjs/lib/warning",
-      "styleq", "styleq/transform-localize-style",
-      "react", "react-dom", "react-dom/client", "nullthrows",
-    ],
-    // The dep optimizer pre-bundles deps with a SEPARATE esbuild pass that
-    // top-level \`define\` doesn't always reach, so a pre-bundled RN dep can
-    // still hit \`__DEV__ is not defined\` under \`lotics app dev\`. Define it
-    // here too — belt-and-suspenders with the top-level \`define\` above.
-    // The optimizer pre-bundles with a SEPARATE esbuild resolver that ignores
-    // \`resolve.extensions\`, so \`.web.js\` must be repeated here or a pre-bundled
-    // RN dep still resolves \`./Picker\` to the native build.
-    esbuildOptions: {
-      define: { __DEV__: "false", global: "globalThis" },
-      resolveExtensions: [".web.tsx", ".web.ts", ".web.js", ".tsx", ".ts", ".jsx", ".js", ".json"],
-    },
-  },
-  build: {
-    outDir: "dist",
-    sourcemap: true,
-    // Top-level await (package projects' generated .lotics/app_fields.ts
-    // resolves the installation binding at module load) needs es2022 — Vite's
-    // default 'modules' baseline is es2020 and esbuild hard-fails TLA there.
-    // Dev already transforms at esnext, so this only aligns the prod build.
-    target: "es2022",
-  },
-  server: {
-    // Allow the sandboxed null-origin iframe used by \`lotics app dev\` to
-    // fetch HMR client + source modules from the dev server. Production
-    // iframe loads modules from api.lotics.ai which already permits null
-    // origin via CORS.
-    cors: { origin: "*" },
-    // @lotics/ui/fonts.css references the API's /iframe/fonts/*.woff2 files
-    // by root-relative URL. A deployed app is served from the API origin so
-    // they resolve directly; under \`lotics app dev\` the app runs on
-    // localhost, so proxy /iframe to the API to load the real fonts.
-    proxy: { "/iframe": { target: "https://api.lotics.ai", changeOrigin: true } },
-  },
-  test: {
-    environment: "jsdom",
-    // RN packages ship Flow (\`import typeof\`) in their native source, reached
-    // transitively by RN-Web components (pickers, calendars, anything touching
-    // Animated). Vitest's web optimizer is OFF by default and ignores the
-    // \`optimizeDeps.resolveExtensions\` above, so it pre-bundles the native
-    // \`.js\` / \`src\` Flow files and esbuild can't parse them. Enable it with the
-    // same \`.web.js\`-first resolution so it bundles the compiled web variants
-    // (Picker.web.js, RN-Web dist) — without this, any test that renders a tree
-    // pulling a Picker / DatePicker fails with "Unexpected token 'typeof'".
-    deps: {
-      optimizer: {
-        web: {
-          enabled: true,
-          // react + react-dom + the @testing-library renderer must ride in the
-          // SAME optimized chunk as react-native-web, so a rendered tree and the
-          // renderer share ONE react instance. Without this, a test that renders a
-          // non-trivial App tree hits a null hooks dispatcher ("Cannot read
-          // properties of null (reading 'useState')") the moment it mounts.
-          include: [
-            "react",
-            "react-dom",
-            "react-dom/client",
-            "react-dom/test-utils",
-            "react-native",
-            "react-native-web",
-            "react-native-svg",
-            "@react-native-picker/picker",
-            "@testing-library/react",
-            "@testing-library/dom",
-            // @lotics/app-sdk ships compiled dist/ JS (unlike @lotics/ui, which
-            // ships source vitest transforms inline) — pre-bundled into its own
-            // chunk, its react import splits from the shared instance and nulls
-            // the hooks dispatcher the instant a hook (useAgentRun / useQuery)
-            // runs in a rendered App tree.
-            "@lotics/app-sdk",
-            // The /router subpath is a SEPARATE optimizer entry — without it,
-            // AppRouter's BrowserRouter bundles apart from the app's
-            // react-router hooks and the Router context never matches
-            // ("useNavigate() may be used only in the context of a <Router>").
-            "@lotics/app-sdk/router",
-            // react-router-dom (App's router) also ships compiled dist JS — pin it
-            // into the shared chunk so its hooks don't split the react instance
-            // ("Invalid hook call") when a test renders the routed App tree.
-            "react-router-dom",
-            // v7: react-router-dom is a thin wrapper — the actual context
-            // lives in react-router; both must ride the shared chunk.
-            "react-router",
-          ],
-          esbuildOptions: {
-            resolveExtensions: [".web.tsx", ".web.ts", ".web.js", ".tsx", ".ts", ".jsx", ".js", ".json"],
-          },
-        },
-      },
-    },
-  },
-});
-`,
-        },
-        {
-            path: "index.html",
-            content: `<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>${escapeHtml(args.app_name)}</title>
-    <style>
-      /*
-       * Full-viewport container chain for iframe apps. Any layout that uses
-       * \`flex: 1\` to fill available space (a scrollable table, list, or
-       * full-page surface) relies on a measured parent height. The browser
-       * default of html/body being content-sized collapses every \`flex: 1\`
-       * to 0 and the surface shrinks to fit only its rendered content.
-       *
-       * Also: #root is made a flex column so the outermost RN \`<View flex:1>\`
-       * inside App.tsx claims the full iframe height.
-       */
-      html, body, #root { height: 100%; margin: 0; }
-      #root { display: flex; flex-direction: column; }
-    </style>
-  </head>
-  <body>
-    <div id="root"></div>
-    <script type="module" src="/src/main.tsx"></script>
-  </body>
-</html>
-`,
-        },
-        {
-            path: "src/main.tsx",
-            content: `import "@lotics/ui/index.css";
-import "@lotics/ui/fonts.css";
-import { PortalHost } from "@lotics/ui/portal";
-import { LoticsLocaleProvider, vi } from "@lotics/ui/locale";
-import { mount } from "@lotics/app-sdk";
-import App from "./App";
-
-// PortalHost is the render target for @lotics/ui overlays (Popover, Tooltip,
-// Dialog). Without it, Portal renders nothing — keep it wrapping the app.
-//
-// LoticsLocaleProvider supplies the kit's own strings (Pagination, sort
-// headers, select-all, the Drawer's record nav…) in one language — Vietnamese
-// by default, since Lotics apps are Vietnamese. Swap to \`en\` (or your own
-// LoticsLocale pack) for another language; remove it to fall back to English.
-mount(
-  <LoticsLocaleProvider locale={vi}>
-    <PortalHost>
-      <App />
-    </PortalHost>
-  </LoticsLocaleProvider>,
-);
-`,
-        },
-        {
-            path: "src/App.tsx",
-            // Default scaffold = a minimal in-app router example (a list screen and a
-            // detail screen), so a new app starts with the recommended routing shape:
-            //   - The app uses react-router via `AppRouter` (from @lotics/app-sdk/router).
-            //     The app owns its own url — embedded, that's the iframe's own url (the
-            //     host never sees it, so navigation never reloads the app); standalone,
-            //     real path URLs. Browser Back/Forward walk app screens in both.
-            //   - The full-container layout pattern is preserved in `Screen`: an outer
-            //     <View flex:1> claims the iframe height (index.html sets
-            //     html/body/#root to 100% + #root is a flex column). Keep that chain
-            //     plain — @lotics/ui/stack wraps children in an unstyled <View> that
-            //     breaks `flex: 1` propagation to a fill-remaining-space child.
-            // A single-screen app can delete the router and render one Screen directly.
-            content: `import type { ReactNode } from "react";
-import { View } from "react-native";
-import { useNavigate, useParams } from "react-router-dom";
-import { AppRouter } from "@lotics/app-sdk/router";
-import { Card } from "@lotics/ui/card";
-import { Text } from "@lotics/ui/text";
-import { Button } from "@lotics/ui/button";
-
-// AppRouter makes the app's screens real URLs — write plain react-router
-// (useNavigate / useParams / <Link>) and it handles both modes. The app owns its
-// own url, so navigation never reloads the app:
-//   - Embedded in the Lotics host: the app drives the iframe's OWN url (invisible
-//     to the user, never seen by the host). Browser Back / Forward walk app
-//     screens; the screen is also mirrored to the host url, so it's shareable and
-//     survives a full refresh (handled by AppRouter — no extra code).
-//   - Standalone at <slug>.lotics.app: a normal browser router with real path URLs.
-
-const ITEMS = [
-  { id: "1", name: "First item" },
-  { id: "2", name: "Second item" },
-  { id: "3", name: "Third item" },
-];
-
-// Outer <View flex:1> claims the full iframe height — works because index.html
-// sets html/body/#root to 100% and #root is a flex column. Keep this flex chain
-// plain (not @lotics/ui/stack) so a fill-remaining-space child can claim height.
-function Screen({ children }: { children: ReactNode }) {
-  return (
-    <View style={{ flex: 1, padding: 24, alignItems: "center" }}>
-      <View style={{ maxWidth: 640, width: "100%", gap: 16 }}>{children}</View>
-    </View>
-  );
-}
-
-function ListScreen() {
-  const navigate = useNavigate();
-  return (
-    <Screen>
-      <Text size="xl" weight="semibold">${escapeHtml(args.app_name)}</Text>
-      <Text color="muted">
-        Tap an item to open its detail screen — the app routes itself. Edit{" "}
-        <Text weight="medium">src/App.tsx</Text> and run{" "}
-        <Text weight="medium">lotics app deploy</Text> to publish.
-      </Text>
-      {ITEMS.map((item) => (
-        <Card key={item.id}>
-          <View
-            style={{
-              padding: 16,
-              flexDirection: "row",
-              alignItems: "center",
-              justifyContent: "space-between",
-              gap: 12,
-            }}
-          >
-            <Text weight="medium">{item.name}</Text>
-            <Button title="Open" color="primary" onPress={() => navigate("/item/" + item.id)} />
-          </View>
-        </Card>
-      ))}
-    </Screen>
-  );
-}
-
-function ItemDetailScreen() {
-  const { id } = useParams();
-  const navigate = useNavigate();
-  const item = ITEMS.find((i) => i.id === id);
-  return (
-    <Screen>
-      {/* An in-app Back control; navigate(-1) walks the history (the browser Back
-          button walks app screens too). */}
-      <View style={{ alignItems: "flex-start" }}>
-        <Button title="Back" onPress={() => navigate(-1)} />
-      </View>
-      <Text size="xl" weight="semibold">{item ? item.name : "Not found"}</Text>
-      <Card>
-        <View style={{ padding: 16, gap: 8 }}>
-          <Text>Detail for item {id}.</Text>
-          <Text color="muted">Reached via in-app navigation, not a host route.</Text>
-        </View>
-      </Card>
-    </Screen>
-  );
-}
-
-const routes = [
-  { path: "/", element: <ListScreen /> },
-  { path: "/item/:id", element: <ItemDetailScreen /> },
-];
-
-export default function App() {
-  return <AppRouter routes={routes} />;
-}
-`,
-        },
-        {
-            // The home for editable workflow bodies. `lotics app pull` writes one
-            // `src/workflows/<alias>.ts` per bound workflow (faithful server source);
-            // edit it, then `lotics app workflow set <alias>` pushes it back through
-            // set_app_workflow (the server verifies). A new app has no bound workflows
-            // yet, so this is just the docked directory + the loop reference. It's a
-            // .md (not a .ts) so tsc's `include: ["src"]` never tries to compile it —
-            // a workflow body is a JS-subset expression over server globals
-            // (trigger / runtime / tool calls) that does NOT typecheck standalone.
-            path: "src/workflows/README.md",
-            content: `# Workflow bodies
-
-Editable JS-subset bodies of this app's workflows live here, one file per alias:
-\`src/workflows/<alias>.ts\`.
-
-## Loop
-
-\`\`\`bash
-lotics app workflow pull          # write/refresh every src/workflows/<alias>.ts from the server
-# edit src/workflows/<alias>.ts
-lotics app workflow check <alias> # typecheck the body locally (same verdict as \`set\`)
-lotics app workflow set <alias>   # push it back through set_app_workflow (the server verifies)
-\`\`\`
-
-\`lotics app pull <app_id>\` also writes these files (alongside the rest of the project).
-
-## What a body is
-
-A workflow body is a **JS-subset expression** that runs server-side using workflow
-globals (\`trigger\`, \`runtime\`, tool calls) and ends with \`return({ data })\`. Each
-pulled file wraps the body in the server's \`__workflow\` envelope and references its
-per-alias ambient globals at \`.lotics/workflows/<alias>.globals.d.ts\`, so it **is**
-locally typecheckable:
-
-\`\`\`bash
-lotics app workflow check        # check every body; [alias] to check one
-\`\`\`
-
-\`check\` builds ONE isolated program per alias (the app's own \`typescript\`, the
-server's compile options — strict, lib es2022 with no DOM), so each body's ambient
-\`trigger\` is unambiguous and the verdict mirrors set-time verify. The main
-\`npm run typecheck\` excludes \`src/workflows\` + \`.lotics/workflows\` (the bodies would
-apply the app's DOM lib, and the per-alias globals collide on \`trigger\`). The
-verification that matters still runs on the **server** when you \`set\` — the same
-guarantee as authoring via \`set_app_workflow\` directly. Edit only the body BETWEEN
-the wrapper lines; the wrapper, the \`/// <reference>\`, and the \`export {};\` marker
-are CLI bookkeeping (stripped on \`set\`). Do not rename a file (the filename is the
-alias the binding is keyed by).
-
-## Authority
-
-\`lotics app deploy\` never authors workflows — it carries code, queries, and
-capabilities only. \`apps.workflows\` has exactly one author: \`set_app_workflow\`
-(which \`lotics app workflow set\` calls). The typed \`inputs\`/\`outputs\` schema for
-each alias lives in \`package.json#lotics.workflows.<alias>\`.
-`,
-        },
-        {
-            path: "src/lucide-react-native.d.ts",
-            content: `// Type shim for lucide-react-native's deep-icon imports
-// (\`lucide-react-native/dist/esm/icons/<name>\`). The package ships JS-only
-// files without per-file .d.ts. The Vite alias in vite.config.ts rewrites
-// these to lucide-react at bundle time; this declaration covers the
-// TypeScript compile-time gap.
-declare module "lucide-react-native/dist/esm/icons/*" {
-  import type { ComponentType } from "react";
-  const Icon: ComponentType<{
-    size: number;
-    color: string;
-    fill?: string;
-    strokeWidth?: number;
-  }>;
-  export default Icon;
-}
-`,
-        },
-        {
-            path: "src/css_modules.d.ts",
-            content: `declare module "*.module.css" {
-  const classes: { [key: string]: string };
-  export default classes;
-}
-
-// Plain side-effect CSS imports (@lotics/ui ships .tsx with import "./x.css").
-declare module "*.css";
-`,
-        },
-        {
-            path: "src/react_native.d.ts",
-            content: `import "react-native";
-
-// Augments react-native's types with the web-only fields @lotics/ui consumes:
-// Pressable's \`hovered\` callback state, plus web-only ViewStyle / TextStyle
-// properties (cursor, outline, boxShadow, etc.) used by its primitives.
-// Each iframe app needs its own copy — TypeScript doesn't auto-pick-up
-// \`.d.ts\` files inside dependencies.
-declare module "react-native" {
-  interface PressableStateCallbackType {
-    hovered: boolean;
-  }
-
-  interface ViewStyle {
-    backdropFilter?: string;
-    backgroundImage?: string;
-    boxShadow?: string;
-    boxSizing?: string;
-    cursor?: string;
-    touchAction?: string;
-    transitionDuration?: string;
-    transitionProperty?: string;
-    appearance?: string;
-    outline?: string;
-    outlineColor?: string;
-    outlineStyle?: string;
-    outlineWidth?: number;
-    outlineOffset?: number;
-  }
-
-  interface TextStyle {
-    outline?: string;
-    outlineColor?: string;
-    outlineStyle?: string;
-    outlineWidth?: number;
-    outlineOffset?: number;
-    appearance?: string;
-  }
-}
-`,
-        },
-        {
-            path: "src/App.test.tsx",
-            content: `import { describe, test, expect } from "vitest";
-import { render } from "@testing-library/react";
-import App from "./App";
-
-describe("App", () => {
-  test("renders the default route", () => {
-    const { container } = render(<App />);
-    expect(container.textContent).toContain("First item");
-  });
-});
-`,
-        },
-        {
-            path: ".github/workflows/ci.yml",
-            content: `name: CI
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-
-jobs:
-  ci:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 22
-      - run: npm ci
-      - run: npm run typecheck
-      - run: npm run lint
-      - run: npm test
-      - run: npm run build
-`,
-        },
-        {
-            path: ".gitignore",
-            content: `node_modules
-dist
-*.tsbuildinfo
-.DS_Store
-.lotics
-coverage
-`,
-        },
-        {
-            path: "README.md",
-            content: `# ${args.app_name}
-
-A Lotics custom-code app. Authored locally, deployed via CLI.
-
-## Develop
-
-\`\`\`bash
-npm install            # already done by 'lotics app create'
-npm run dev            # local Vite dev server (UI only — real data needs deploy)
-\`\`\`
-
-## Quality
-
-\`\`\`bash
-npm run typecheck      # tsc --noEmit
-npm run lint           # oxlint
-npm test               # vitest run
-\`\`\`
-
-CI runs all three on every PR via \`.github/workflows/ci.yml\`.
-
-## Deploy
-
-\`\`\`bash
-lotics app deploy              # build + upload as a new version
-lotics app deploy -m "what"    # with a commit-message-style note
-\`\`\`
-
-## SDK + UI components
-
-\`\`\`tsx
-import { mount, useQuery, useWorkflow } from "@lotics/app-sdk";
-import { Stack } from "@lotics/ui/stack";
-import { Card } from "@lotics/ui/card";
-import { Button } from "@lotics/ui/button";
-import { Text } from "@lotics/ui/text";
-// ... and Grid, Dialog, DatePicker, FormPicker, BarChart, LineChart, PieChart, Metric, ProgressBar, etc.
-\`\`\`
-
-@lotics/ui ships React Native primitives that render via react-native-web
-in this Vite app (the alias is preconfigured in \`vite.config.ts\`). See
-the full export list at https://www.npmjs.com/package/@lotics/ui.
-
-## Routing
-
-\`src/App.tsx\` ships a minimal in-app router. Write plain react-router and wrap
-your routes in \`AppRouter\` from \`@lotics/app-sdk/router\` — the app owns its own
-url, so navigation never reloads the app. Embedded in the Lotics host it drives
-the iframe's own url (invisible to the user, never seen by the host); browser
-Back/Forward walk app screens, and the screen is mirrored to the host url so it's
-shareable and survives a full refresh. Standalone (\`<slug>.lotics.app\`) it's a
-normal browser router with real path URLs. A single-screen app can drop the
-router and render one screen directly.
-
-See https://lotics.ai/docs/app-sdk for the SDK reference.
-`,
-        },
-    ];
-}
-function escapeHtml(s) {
-    return s.replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;");
-}