@ishlabs/cli 0.26.0 → 0.26.1

package/dist/lib/local-sim/types.d.ts

@@ -12,10 +12,12 @@ export interface LocalSimInitRequest {
     iteration_id: string;
 }
 export interface IterationDetails {
-    url: string;
+    url?: string;
     platform: string;
     screen_format: "desktop" | "mobile_portrait";
     locale?: string;
+    /** Native (ios/android): the app target to install/launch (bundle id / package / path). */
+    app_artifact?: string;
 }
 export interface LocalSimInitResponse {
     participant_id: string;
@@ -221,6 +223,14 @@ export interface RecordInteraction {
     assignment_status: AssignmentStatus;
     tabs?: LocalTabInfo[];
 }
+export interface LocalSimInteractionRequest {
+    participant_id: string;
+    product_id: string;
+    interaction: RecordInteraction;
+}
+export interface LocalSimInteractionResponse {
+    interaction_id: string;
+}
 export interface AssignmentStatusUpdate {
     assignment_id: string;
     status: string;
@@ -229,7 +239,6 @@ export interface AssignmentStatusUpdate {
 export interface LocalSimRecordRequest {
     participant_id: string;
     product_id: string;
-    interactions: RecordInteraction[];
     final_status: string;
     assignment_statuses: AssignmentStatusUpdate[];
 }

package/dist/lib/paths.d.ts

@@ -20,4 +20,10 @@ export declare function cloudflaredBin(): string;
 export declare function wdaDir(): string;
 /** Stamp file recording which CLI/runner version the cached WDA bundle is for. */
 export declare function wdaVersionFile(): string;
+/**
+ * Path to `adb` inside Google's standalone Android platform-tools, when we've
+ * fetched it into `binDir()` on demand (the zip unpacks a `platform-tools/`
+ * dir). Mirrors `cloudflaredBin()` / `wdaDir()`.
+ */
+export declare function adbBin(): string;
 export declare function connectLockPath(): string;

package/dist/lib/paths.js

@@ -46,6 +46,15 @@ export function wdaDir() {
 export function wdaVersionFile() {
     return path.join(wdaDir(), "VERSION");
 }
+/**
+ * Path to `adb` inside Google's standalone Android platform-tools, when we've
+ * fetched it into `binDir()` on demand (the zip unpacks a `platform-tools/`
+ * dir). Mirrors `cloudflaredBin()` / `wdaDir()`.
+ */
+export function adbBin() {
+    const exe = process.platform === "win32" ? "adb.exe" : "adb";
+    return path.join(binDir(), "platform-tools", exe);
+}
 export function connectLockPath() {
     return path.join(rootDir(), "connect.lock");
 }

package/dist/lib/report-readiness.d.ts

@@ -0,0 +1,44 @@
+/**
+ * Best-effort readiness reporting to the ish backend.
+ *
+ * After the CLI computes its native-simulation readiness checks (the same
+ * array `ish check <platform> --json` emits), we POST them to
+ * `${apiUrl}/api/v1/connect/device` so the ish web app can render a live
+ * native-readiness panel. This is the native analog of how `ish connect
+ * <port>` registers a cloudflare tunnel: a side-channel that tells the
+ * backend "this developer's machine is (or isn't) ready to drive a native
+ * iOS/Android simulation right now."
+ *
+ * Contract (must match the backend exactly):
+ *
+ *   POST /api/v1/connect/device
+ *   {
+ *     "platform":    "ios" | "android",
+ *     "checks":      [ {key,name,group,status,message?,fix?}, ... ],
+ *     "overall":     "pass" | "warn" | "fail" | "skip",
+ *     "cli_version": "<package.json version>"
+ *   }
+ *
+ * This is COMPLETELY best-effort. It never throws, never blocks the command,
+ * never writes to stdout, and silently returns when the user isn't logged in
+ * or is offline. The CLI's normal output and exit code are unaffected. The
+ * only side-channel is an optional stderr line under a `debug` flag, mirroring
+ * how connect.ts logs its own warnings.
+ */
+import type { GlobalOpts } from "./command-helpers.js";
+import type { Check, CheckStatus } from "../commands/doctor.js";
+/**
+ * POST the platform-scoped readiness checks to the backend. Best-effort:
+ * resolves auth + posts inside a single try/catch, swallowing every error.
+ *
+ * @param platform  The native platform the checks were scoped to.
+ * @param checks    The exact `runChecks()` array (already scoped to `platform`).
+ * @param overall   The aggregate status (`overall(checks)`).
+ * @param globals   Resolved CLI globals — used only for `--api-url` / `--dev`
+ *                  / `--token` resolution. Pass the command's `globals`.
+ * @param opts.debug  When true, log a one-line failure note to stderr (off by
+ *                    default so the post is silent). Mirrors connect.ts.
+ */
+export declare function reportReadiness(platform: "ios" | "android", checks: Check[], overall: CheckStatus, globals: Pick<GlobalOpts, "apiUrl" | "dev" | "token" | "tokenFile">, opts?: {
+    debug?: boolean;
+}): Promise<void>;

package/dist/lib/report-readiness.js

@@ -0,0 +1,74 @@
+/**
+ * Best-effort readiness reporting to the ish backend.
+ *
+ * After the CLI computes its native-simulation readiness checks (the same
+ * array `ish check <platform> --json` emits), we POST them to
+ * `${apiUrl}/api/v1/connect/device` so the ish web app can render a live
+ * native-readiness panel. This is the native analog of how `ish connect
+ * <port>` registers a cloudflare tunnel: a side-channel that tells the
+ * backend "this developer's machine is (or isn't) ready to drive a native
+ * iOS/Android simulation right now."
+ *
+ * Contract (must match the backend exactly):
+ *
+ *   POST /api/v1/connect/device
+ *   {
+ *     "platform":    "ios" | "android",
+ *     "checks":      [ {key,name,group,status,message?,fix?}, ... ],
+ *     "overall":     "pass" | "warn" | "fail" | "skip",
+ *     "cli_version": "<package.json version>"
+ *   }
+ *
+ * This is COMPLETELY best-effort. It never throws, never blocks the command,
+ * never writes to stdout, and silently returns when the user isn't logged in
+ * or is offline. The CLI's normal output and exit code are unaffected. The
+ * only side-channel is an optional stderr line under a `debug` flag, mirroring
+ * how connect.ts logs its own warnings.
+ */
+import { resolveApiUrl, resolveToken } from "./auth.js";
+import { ApiClient } from "./api-client.js";
+import pkg from "../../package.json" with { type: "json" };
+/** Backend endpoint (relative to the `/api/v1` base ApiClient prepends). */
+const DEVICE_ENDPOINT = "/connect/device";
+/**
+ * POST the platform-scoped readiness checks to the backend. Best-effort:
+ * resolves auth + posts inside a single try/catch, swallowing every error.
+ *
+ * @param platform  The native platform the checks were scoped to.
+ * @param checks    The exact `runChecks()` array (already scoped to `platform`).
+ * @param overall   The aggregate status (`overall(checks)`).
+ * @param globals   Resolved CLI globals — used only for `--api-url` / `--dev`
+ *                  / `--token` resolution. Pass the command's `globals`.
+ * @param opts.debug  When true, log a one-line failure note to stderr (off by
+ *                    default so the post is silent). Mirrors connect.ts.
+ */
+export async function reportReadiness(platform, checks, overall, globals, opts = {}) {
+    try {
+        const apiUrl = resolveApiUrl(globals.apiUrl, globals.dev);
+        // resolveToken throws when the user isn't logged in (or a network blip
+        // prevents an expired-token refresh) — that throw is caught below and we
+        // silently return, exactly as required for the offline / logged-out case.
+        const token = await resolveToken(globals.token, apiUrl, globals.tokenFile);
+        const client = new ApiClient({ apiUrl, token });
+        await client.post(DEVICE_ENDPOINT, {
+            platform,
+            checks,
+            overall,
+            cli_version: pkg.version,
+        }, 
+        // Tight timeout: `ish check` awaits this so the beacon lands before the
+        // process exits, but the panel POST must never stall the command. 2.5s
+        // is plenty on a healthy backend and bounds the worst case if the host
+        // is unreachable or hung.
+        { timeout: 2_500 });
+    }
+    catch (err) {
+        // Swallow everything. A logged-out user, an offline machine, an old
+        // backend without the endpoint, a 5xx — none of it should ever surface
+        // to the user or change the command's behavior.
+        if (opts.debug) {
+            const reason = err instanceof Error ? err.message : String(err);
+            console.error(`(readiness report skipped: ${reason})`);
+        }
+    }
+}

package/dist/lib/skill-content.js

@@ -230,6 +230,8 @@ To hand a study to someone **without an ish account** — a prospect, a stakehol
 - **\`ish person create\` accepts inline flags** (mirrors \`person update\`): the file-only API (\`--file <path>\`) is preserved as an escape hatch but the common path is \`ish person create --name "X" --type ai --country US ...\` — \`--type\` defaults to \`ai\` when \`--file\` is omitted. See \`ish person create --help\` for the full inline-flag set including \`--household\` (MECE rule applies) and \`--accessibility-profile\`.
 - **\`ish status\` now surfaces \`chat_endpoint\`** alongside \`workspace\`/\`study\`/\`ask\`. Stale or orphan active refs get a \`warning\` + \`hint\` field on the affected ref (instead of silently dropping the \`name\`). On \`workspace use <other>\`, the CLI cascade-clears \`study\`/\`ask\`/\`chat_endpoint\` (they belong to the previous workspace).
 - **Share link URL host ≠ API host**: \`ish study share\` prints the backend-built \`share_url\` (the web frontend host). Use it verbatim — never reconstruct the URL from the API host or app URL; they differ. \`ish study unshare\` takes the **raw token** (from \`study share\` / \`study share --list\`), not a study id or alias.
+- **Native app iterations (ios/android) name the app, not a URL**: \`ish iteration create --platform ios --app <bundle-id>\` stores the target as \`app_artifact\` (no URL). The iteration remembers it, so \`ish study run --local\` needs **no \`--app\` on reruns** (it defaults from the iteration). Pass \`--app <path-to.app|.apk>\` only to override with a fresh local build. \`--app\` is optional at create time (omit it for "chosen at run time"). Only \`browser\`/\`figma\` iterations require \`--url\`.
+- **Local runs have no server-side screenshots**: \`ish study run --local\` (including ios/android) writes a per-step HTML debug report to \`~/.ish/debug/sim-*.html\` (path printed at the end of the run) instead of pushing screenshots to the server. \`ish study screenshots list\` on a local-only study finds none — open the debug report instead.
 
 ## When in doubt
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ishlabs/cli",
-  "version": "0.26.0",
+  "version": "0.26.1",
   "description": "The command-line interface for ish",
   "type": "module",
   "bin": {