@lotics/cli 0.60.1 → 0.62.1

package/dist/starter_template.js

@@ -108,7 +108,9 @@ export function buildStarterTemplate(args) {
                     "@vitejs/plugin-react": "^4.3.0",
                     jsdom: "^25.0.0",
                     oxlint: "^0.13.0",
-                    typescript: "^5.6.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",
                 },
@@ -148,41 +150,17 @@ export function buildStarterTemplate(args) {
                 // base, which IS read. (GAP-38.)
                 include: ["src", ".lotics/**/*"],
                 // src/workflows/<alias>.ts bodies run on the server (workflow globals:
-                // trigger / runtime / tool calls). They ARE locally typecheckable —
-                // each is wrapped in the server's `__workflow` envelope and references
-                // its per-alias `.lotics/workflows/<alias>.globals.d.ts` — but under a
-                // DEDICATED config that mirrors the server's compile options (es2022
-                // lib, NO DOM). The main `npm run typecheck` excludes them so it stays
-                // green and DOM-lib-free for bodies; check a body with
-                // `tsc -p tsconfig.workflows.json`. The server is the single verifier
-                // on `lotics app workflow set`.
-                exclude: ["node_modules", "src/workflows"],
-            }, null, 2) + "\n",
-        },
-        {
-            // Dedicated config for the editable workflow bodies (GAP-59). Mirrors the
-            // SERVER's set-time typecheck options (strict, lib es2022 with NO DOM,
-            // target ES2022, skipLibCheck) so a local `tsc -p tsconfig.workflows.json`
-            // gives the same verdict the server would on `lotics app workflow set`.
-            // Each body file is a module (the CLI writes a bookkeeping `export {};`),
-            // so the per-file `__workflow` wrapper doesn't collide across bodies.
-            path: "tsconfig.workflows.json",
-            content: JSON.stringify({
-                compilerOptions: {
-                    target: "ES2022",
-                    lib: ["ES2022"],
-                    module: "ESNext",
-                    moduleResolution: "Bundler",
-                    strict: true,
-                    skipLibCheck: true,
-                    noEmit: true,
-                    types: [],
-                },
-                // The bodies + their per-alias ambient globals. `.lotics/workflows`
-                // uses the explicit `**/*` glob for the same dot-dir walk reason the
-                // main config does (TS's include walk skips bare dot-dirs).
-                include: ["src/workflows", ".lotics/workflows/**/*"],
-                exclude: ["node_modules"],
+                // 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",
         },
         {
@@ -540,6 +518,7 @@ Editable JS-subset bodies of this app's workflows live here, one file per alias:
 \`\`\`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)
 \`\`\`
 
@@ -551,15 +530,17 @@ A workflow body is a **JS-subset expression** that runs server-side using workfl
 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 — under the dedicated config that mirrors the server's compile
-options:
+locally typecheckable:
 
 \`\`\`bash
-tsc -p tsconfig.workflows.json   # same verdict the server gives on \`set\`
+lotics app workflow check        # check every body; [alias] to check one
 \`\`\`
 
-The main \`npm run typecheck\` excludes \`src/workflows\` (it would apply the app's
-DOM lib, which the server doesn't), so the bodies have their own config. The
+\`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
@@ -599,6 +580,9 @@ declare module "lucide-react-native/dist/esm/icons/*" {
   const classes: { [key: string]: string };
   export default classes;
 }
+
+// Plain side-effect CSS imports (@lotics/ui ships .tsx with import "./x.css").
+declare module "*.css";
 `,
         },
         {

package/dist/starter_template.test.js

@@ -97,15 +97,19 @@ describe("buildStarterTemplate", () => {
         const config = fileNamed(buildStarterTemplate(baseArgs), "vite.config.ts");
         expect(config).toMatch(/include:\s*\[[\s\S]*"react-router-dom"/);
     });
-    test("ships a dedicated tsconfig.workflows.json mirroring the server's compile options (GAP-59)", () => {
-        const cfg = JSON.parse(fileNamed(buildStarterTemplate(baseArgs), "tsconfig.workflows.json"));
-        // Server-mirroring: es2022 lib with NO DOM, strict, skipLibCheck, target ES2022.
-        expect(cfg.compilerOptions.lib).toEqual(["ES2022"]);
-        expect(cfg.compilerOptions.strict).toBe(true);
-        expect(cfg.compilerOptions.skipLibCheck).toBe(true);
-        expect(cfg.compilerOptions.target).toBe("ES2022");
-        // It includes the bodies + their per-alias ambient globals.
-        expect(cfg.include).toContain("src/workflows");
-        expect(cfg.include).toContain(".lotics/workflows/**/*");
+    test("main tsconfig excludes BOTH the workflow bodies and their per-alias globals (GAP-59 fix)", () => {
+        // npm run typecheck must skip src/workflows (DOM-lib skew) AND .lotics/workflows
+        // (the per-alias ambient `trigger` declarations collide across aliases and
+        // report false errors). Bodies are checked by `lotics app workflow check`.
+        const cfg = JSON.parse(fileNamed(buildStarterTemplate(baseArgs), "tsconfig.json"));
+        expect(cfg.exclude).toContain("src/workflows");
+        expect(cfg.exclude).toContain(".lotics/workflows");
+    });
+    test("no longer ships the all-in-one tsconfig.workflows.json (it collided per-alias globals)", () => {
+        // The dedicated config compiled every alias's globals into ONE program, so the
+        // ambient `trigger` declarations collided. `lotics app workflow check` replaces
+        // it with one isolated program per alias.
+        const files = buildStarterTemplate(baseArgs);
+        expect(files.find((f) => f.path === "tsconfig.workflows.json")).toBeUndefined();
     });
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.60.1",
+  "version": "0.62.1",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {
@@ -25,6 +25,7 @@
     "@lotics/xlsx": "*",
     "@types/node": "^22.15.21",
     "esbuild": "^0.28.1",
+    "typescript": "^6.0.3",
     "vitest": "^4.1.7"
   },
   "keywords": [