@lotics/cli 0.57.0 → 0.62.0

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",
                 },
@@ -147,7 +149,18 @@ export function buildStarterTemplate(args) {
                 // fall to `unknown`. The explicit glob makes the dot-dir the non-wildcard
                 // base, which IS read. (GAP-38.)
                 include: ["src", ".lotics/**/*"],
-                exclude: ["node_modules"],
+                // 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",
         },
         {
@@ -483,6 +496,63 @@ const routes = [
 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>\`.
 `,
         },
         {

package/dist/starter_template.test.js

@@ -97,4 +97,19 @@ describe("buildStarterTemplate", () => {
         const config = fileNamed(buildStarterTemplate(baseArgs), "vite.config.ts");
         expect(config).toMatch(/include:\s*\[[\s\S]*"react-router-dom"/);
     });
+    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.57.0",
+  "version": "0.62.0",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {
@@ -21,9 +21,11 @@
   },
   "devDependencies": {
     "@lotics/docx": "*",
+    "@lotics/shared": "*",
     "@lotics/xlsx": "*",
     "@types/node": "^22.15.21",
     "esbuild": "^0.28.1",
+    "typescript": "^6.0.3",
     "vitest": "^4.1.7"
   },
   "keywords": [