@ait-co/devtools 0.1.137 → 0.1.139

package/dist/test-runner/relay-factory.d.ts

@@ -11105,8 +11105,36 @@ interface RelayConnectionFactoryOptions {
    * intoss-private:// scheme URL from `ait deploy --scheme-only` (env3). The
    * phone cold-loads the candidate bundle this URL points at. SECRET-HANDLING:
    * never logged.
+   *
+   * Ignored when {@link attachLauncher} is `true` — the env-2 launcher path
+   * builds its attach URL from {@link appUrl} + the relay wss, not a scheme URL.
+   * Pass `''` in that case.
    */
   schemeUrl: string;
+  /**
+   * env-2 (AITC Sandbox PWA) attach mode (devtools#774). When `true`, `open()`
+   * builds the attach URL as a **launcher deep-link**
+   * (`buildLauncherAttachUrl(appUrl, wssUrl, totp)` — the same env-2 path the
+   * MCP daemon takes via `prepareAttach(deps, 'relay-mobile', …)`, issue #378)
+   * instead of an intoss-private scheme deep-link. The relay boot, QR
+   * rendering, dashboard, and attach-wait are byte-for-byte identical to env 3;
+   * only the URL family differs. Omitted/false keeps the env-3 scheme path
+   * unchanged (zero behavior change).
+   */
+  attachLauncher?: boolean;
+  /**
+   * The consumer dev server's HTTP tunnel URL (e.g. an sdk-example
+   * `dev:phone:cdp` `*.trycloudflare.com` URL) that the launcher PWA frames.
+   * REQUIRED when {@link attachLauncher} is `true`; ignored otherwise.
+   *
+   * Threaded to the `relay-mobile` `prepareAttach` branch via the
+   * `AIT_TUNNEL_BASE_URL` env var (the same key the MCP daemon reads), so the
+   * exact same env-2 assembly runs — no divergent code path.
+   *
+   * SECRET-HANDLING: this is a tunnel host at the same sensitivity as the relay
+   * wss — NEVER logged. It rides only inside the QR/dashboard attach capsule.
+   */
+  appUrl?: string;
   /**
    * Project root for the `.ait_relay` secret lookup (read-only). Defaults to
    * `process.cwd()`.
@@ -11143,6 +11171,30 @@ interface RelayConnectionFactoryOptions {
    * absence the same as `false`). Not a secret.
    */
   stubBlocking?: boolean;
+  /**
+   * Injects `__AIT_PACE_MS__ = paceMs` before the first test bundle runs
+   * (devtools#767) — `runtime.ts`'s test-execution loop reads this page
+   * global and waits `paceMs` before every test after the first one that
+   * actually runs. Optional — omitted/0 means no flag is injected, which is
+   * byte-for-byte the pre-#767 behavior (the loop treats an absent/non-
+   * positive value as "no pacing"). Not a secret. This is the PAGE-side half
+   * of `--pace`; the RUNNER-side (file-to-file) half is a plain `opts.paceMs`
+   * forwarded to `runTestFilesOverRelay` by the caller (cli.ts) — this
+   * factory only owns the page-global injection.
+   */
+  paceMs?: number;
+  /**
+   * Injects `__AIT_PACE_METHOD_MS__ = paceMethodMs` before the first test
+   * bundle runs (devtools#769) — `bundle.ts`'s sdk-redirect virtual module
+   * reads this page global via `method-pace.ts#getPaceMethodMs()` and paces
+   * every SDK call to a minimum interval BETWEEN calls to the SAME named
+   * function, independent of `--pace`'s test-to-test/file-to-file spacing.
+   * Optional — omitted/0 means no flag is injected, which is byte-for-byte
+   * the pre-#769 behavior (`getPaceMethodMs()` treats an absent/non-positive
+   * value as "no pacing", and `wrapWithMethodPacing` returns the SDK object
+   * untouched in that case). Not a secret.
+   */
+  paceMethodMs?: number;
   /**
    * Overrides the dashboard HTTP server's bind base port (devtools#752).
    * Threaded straight through to `startQrHttpServer`'s `dashboardPort`
@@ -11170,12 +11222,13 @@ interface RelayConnectionFactoryOptions {
   onQrContent: (textChunks: string[]) => void;
 }
 /**
- * Builds a {@link RelayConnectionFactory} that opens a standalone env3 relay
- * connection.
+ * Builds a {@link RelayConnectionFactory} that opens a standalone relay
+ * connection for env 3 (intoss-private scheme, default) or env 2 (AITC Sandbox
+ * PWA launcher deep-link, when `opts.attachLauncher` is set — devtools#774).
  *
  * `open()` performs the full attach lifecycle and BLOCKS while a human scans
- * the rendered QR with their phone — there is no way around the manual scan
- * for env3. By default the wait is UNBOUNDED (`opts.timeoutMs` omitted): the
+ * the rendered QR with their phone — there is no way around the manual scan.
+ * By default the wait is UNBOUNDED (`opts.timeoutMs` omitted): the
  * runner stays up until the user stops it (Ctrl-C/SIGTERM), since QR-scan is
  * a human-paced action with no sound default bound (devtools#735). Passing an
  * explicit `timeoutMs` opts into the old bounded behavior (CI/headless