@codeam/shared 2.76.22 → 2.76.24

package/dist/index.d.mts

@@ -1473,6 +1473,17 @@ interface PreviewDetection {
         args: string[];
     }>;
     notes?: string;
+    /**
+     * Project-relative directory the dev server (and `setup_commands`, and the
+     * Node deps pre-flight) runs in — for an app that lives in a subfolder of
+     * the workspace (`teleshop/` with its own `.venv`). Absent or `'.'` = the
+     * workspace root, the behaviour before this field existed. `command` paths
+     * like `.venv/bin/python` resolve against it. The CLI refuses a value that
+     * escapes the workspace or doesn't exist. Additive: older CLIs ignore it,
+     * and the apps carry it through untouched (the confirm sheet spreads the
+     * detection it was given).
+     */
+    cwd?: string;
     /**
      * Every runnable dev-style script the CLI found in the repo (root + each
      * workspace app), so the confirm sheet can offer them in an autocomplete

package/dist/index.d.ts

@@ -1473,6 +1473,17 @@ interface PreviewDetection {
         args: string[];
     }>;
     notes?: string;
+    /**
+     * Project-relative directory the dev server (and `setup_commands`, and the
+     * Node deps pre-flight) runs in — for an app that lives in a subfolder of
+     * the workspace (`teleshop/` with its own `.venv`). Absent or `'.'` = the
+     * workspace root, the behaviour before this field existed. `command` paths
+     * like `.venv/bin/python` resolve against it. The CLI refuses a value that
+     * escapes the workspace or doesn't exist. Additive: older CLIs ignore it,
+     * and the apps carry it through untouched (the confirm sheet spreads the
+     * detection it was given).
+     */
+    cwd?: string;
     /**
      * Every runnable dev-style script the CLI found in the repo (root + each
      * workspace app), so the confirm sheet can offer them in an autocomplete

package/dist/index.js

@@ -3266,13 +3266,16 @@ Analyze the project in the current working directory and return how to start
 its development server for in-app preview.
 
 Read package.json, Procfile, Dockerfile, docker-compose.yml, manage.py, app.json,
-mix.exs, Cargo.toml, go.mod, requirements.txt, Gemfile, and any other framework
-markers you find at depth <= 2.
+mix.exs, Cargo.toml, go.mod, requirements.txt, pyproject.toml, Gemfile, and any
+other framework markers you find at depth <= 2. The app may live in a subfolder
+(e.g. teleshop/requirements.txt with nothing runnable at the root) \u2014 look there
+too.
 
 Return ONLY a JSON object on stdout (no prose, no markdown fences):
 
 {
   "framework": "<name, or 'unsupported'>",
+  "cwd": "<folder the dev server runs in, relative to the current directory; '.' for the root>",
   "command": "<executable>",
   "args": ["..."],
   "port": <number>,
@@ -3284,6 +3287,13 @@ Return ONLY a JSON object on stdout (no prose, no markdown fences):
 
 Rules:
 - Pick the script the developer would run locally to see the app (typically "dev", "start", "serve").
+- If the app lives in a subfolder, set "cwd" to that folder (e.g. "teleshop"). command,
+  args and setup_commands then run INSIDE it: write paths relative to it
+  (".venv/bin/python", not "teleshop/.venv/bin/python"), and never wrap the command
+  in "cd \u2026 &&" or "sh -c" \u2014 it is executed directly, without a shell.
+- Python: use the project's virtualenv interpreter when one exists
+  (".venv/bin/python" with args ["-m","uvicorn","main:app","--host","0.0.0.0","--port","8000"]),
+  otherwise "python3".
 - Prefer binding to 0.0.0.0 \u2014 most frameworks default to localhost which the tunnel cannot reach.
 - For Expo: framework="Expo", command="npx", args=["expo","start","--tunnel"], port=8081, notes="Scan QR with Expo Go".
 - If no dev server applies (CLI library, lambda, batch script): {"framework":"unsupported","notes":"<reason>"}.