@tapi-dev/sdk 0.1.39 → 0.1.44

package/README.md

@@ -17,9 +17,8 @@ locally and `tapi` is not on `PATH`, use `npx tapi` as a fallback.
 
 Tapi Studio is launched from the signed-in developer account. Running
 `tapi studio` lists the Tapps available to that account, asks which one to open,
-then starts Studio in that Tapp context. The current directory can still provide
-a default via `.tapi/project.json`, but it is no longer required for Studio to
-know which Tapp to show.
+then starts Studio in that Tapp context. Studio no longer reads project identity
+from the current directory.
 
 ```bash
 npm install @tapi-dev/sdk
@@ -66,8 +65,6 @@ Useful commands:
 
 ```bash
 tapi login
-tapi init --project brokerage
-tapi link --project brokerage
 tapi studio
 tapi studio --tapp brokerage
 tapi service install --channel pilot
@@ -75,21 +72,14 @@ tapi service status
 tapi services describe schwab.place_order
 tapi tapp create brokerage
 tapi queue create "John"
-tapi tapp queue add brokerage queue_abc123
-tapi runner setup --runner-id john-laptop --project brokerage
-tapi runner slot set john-laptop 1 queue_abc123 --project brokerage
+tapi runner gui
+tapi runner setup --runner-id john-laptop
+tapi runner slot set john-laptop 1 queue_abc123
 tapi tapp service add brokerage schwab.place_order --service-map sm_123 --entry place_order
 tapi triggers sync
 tapi sessions
 ```
 
-Local project identity lives in the app repo:
-
-```text
-.tapi/project.json
-.tapi/services/catalog.json
-```
-
 ServiceMaps and service-run contracts are saved in the bound Tapi server
 project. Runtime SDK calls read the service catalog from that project.
 
@@ -100,32 +90,39 @@ tapi tapp service add brokerage schwab.place_order \
   --entry place_order
 ```
 
-Create a queue, attach it to the Tapp, and point one or more runner slots at
-that queue:
+Create a queue and point one or more runner slots at that queue. Your app or
+Tapp user supplies the same queue id when it starts a service run:
 
 ```bash
-tapi queue create "John" --project brokerage
-tapi tapp queue add brokerage queue_abc123
+tapi queue create "John"
 
-tapi runner slot set john-laptop 1 queue_abc123 \
-  --project brokerage
+tapi runner slot set john-laptop 1 queue_abc123
 ```
 
-For users setting up a local runner, `tapi runner setup` opens a localhost setup
-page that can create or accept a queue id, attach that queue to the Tapp, and
-assign one or more slots on the runner:
+For users setting up a local runner on Windows, open the installed desktop app
+from Start by searching for `Tapi Runner`, or launch it from the CLI:
+
+```bash
+tapi runner gui
+```
+
+The desktop app reads the local runner identity, creates Railway queues, assigns
+queue ids to runner slots, and copies queue ids so they can be pasted into the
+Tapp/user setup flow.
+
+`tapi runner setup` is kept as a legacy localhost setup page for development and
+automation fallback:
 
 ```bash
 tapi runner setup \
-  --runner-id john-laptop \
-  --project brokerage
+  --runner-id john-laptop
 ```
 
 ## Quick Start
 
 Create one TAPI client in server-side app code. Use a Firebase ID token for the
-developer identity that owns and pays for the Tapp, the Tapp id that owns the
-service call, and optionally the same project id from `.tapi/project.json`.
+developer identity that owns and pays for the Tapp, plus the Tapp id that owns
+the service call.
 
 ```ts
 import { TapiClient } from "@tapi-dev/sdk";
@@ -165,7 +162,7 @@ const tapi = new TapiClient({
 });
 ```
 
-Inspect preserved sessions from the repo:
+Inspect preserved sessions:
 
 ```bash
 tapi sessions
@@ -185,8 +182,7 @@ and selecting inputs/outputs. The SDK sees the public service-run name:
 ```
 
 A service run is routed through a queue. The queue id is the only routing handle:
-the Tapp must attach the queue, and one or more runner slots must be configured
-with the same queue id.
+one or more runner slots must be configured with the same queue id.
 
 ```ts
 const operation = await tapi.services.describe("schwab.place_order");
@@ -266,8 +262,8 @@ the website itself should stay as normal service outputs.
 
 ## Service Triggers
 
-Triggers are scheduled service runs. Keep trigger definitions in the app repo
-and sync them with the service catalog from that repo:
+Triggers are scheduled service runs. Keep trigger definitions in the app repo
+and sync them with an explicit Tapp/project context:
 
 ```ts
 // tapi.config.ts
@@ -284,12 +280,11 @@ export default {
 ```
 
 ```bash
-tapi triggers sync
-```
-
-`triggers sync` upserts by trigger name for the current `.tapi/project.json`
-project. Schedules support standard five-field cron strings or intervals as
-numbers of seconds / strings like `30s`, `15m`, `2h`, and `1d`.
+tapi triggers sync --project brokerage
+```
+
+`triggers sync` upserts by trigger name for the selected project. Schedules support standard five-field cron strings or intervals as
+numbers of seconds / strings like `30s`, `15m`, `2h`, and `1d`.
 
 You can also manage triggers directly:
 
@@ -342,7 +337,7 @@ await tapi.services.run("walmart.reorder", {
 ```
 
 Use `TempProfile` for throwaway work. Temp profiles can be cloned from a
-template profile and assigned different proxies:
+template profile and different proxies:
 
 ```ts
 const temp = await tapi.runtime.tempProfiles.provisionMany({
@@ -399,7 +394,7 @@ TAPI_PROJECT_ID=brokerage
 ```
 
 `tappId` is required. Service calls are made for that Tapp, and the developer
-who owns the Tapp pays for the service delivery. If provided, `projectId` is
+who owns the Tapp pays for the service runner. If provided, `projectId` is
 sent as the `X-Tapi-Project` header and the server rejects mismatches.
 
 ## Common Project Setup

package/dist/cli.d.ts

@@ -1,6 +1,5 @@
 #!/usr/bin/env node
 import type { TapiDevSession } from "./types.js";
-import { type TapiWorkspace } from "./workspace.js";
 export declare const PORTABLE_STUDIO_SERVER_READY_TIMEOUT_MS = 120000;
 export type StudioChannel = "pilot" | "stable" | "nightly";
 export interface StudioReleaseManifest {
@@ -62,11 +61,9 @@ export interface StudioCliOptions {
     exePath?: string;
     installToken?: string;
     installTokenSource?: "option" | "env" | "minted";
-    workspace?: TapiWorkspace;
-    workspaceRoot?: string;
     projectId?: string;
     projectSlug?: string;
-    projectIdSource?: "option" | "env" | "workspace" | "selection";
+    projectIdSource?: "option" | "env" | "selection";
     workspaceMode: boolean;
     launchUrlQuery?: string;
     tappSelectionMode: "auto" | "select" | "last" | "none";
@@ -74,7 +71,6 @@ export interface StudioCliOptions {
 export interface RunnerSetupCliOptions {
     apiBaseUrl: string;
     authToken?: string;
-    projectId: string;
     runnerId: string;
     port: number;
     openBrowser: boolean;
@@ -89,7 +85,6 @@ export interface RunnerSetupAction {
 export interface RunnerSetupActionResult {
     queueId: string;
     queue: Record<string, unknown>;
-    attachment: Record<string, unknown>;
     slots: Record<string, unknown>[];
 }
 export interface RunnerSetupServerHandle {
@@ -148,10 +143,12 @@ export declare function validateStudioManifest(input: unknown): StudioReleaseMan
 export declare function validateServiceReleaseManifest(input: unknown): ServiceReleaseManifest;
 export declare function compareVersions(left: string, right: string): number;
 export declare function memoizeStudioInstallToken(options: StudioCliOptions, installToken?: string, source?: StudioCliOptions["installTokenSource"]): string;
+export declare function resolveStudioTappSelection(options: StudioCliOptions): Promise<StudioCliOptions>;
 export declare function closeExistingPortableStudioServersForFreshLaunch(stopProcesses?: () => Promise<number>): Promise<{
     stopped: number;
     recordsRemoved: number;
 }>;
+export declare function studioServerLaunchArgs(): string[];
 export declare function findPortablePlaywrightBrowsersDir(exePath: string): string | undefined;
 export declare function waitForHttpOk(url: string, timeoutMs?: number, intervalMs?: number, fetchImpl?: FetchLike): Promise<void>;
 export declare function chooseStudioPort(preferred?: number, options?: {