fix(sdk): drop triggerAndSubscribe from TriggerClient surface

`triggerAndSubscribe_internal` requires `taskContext.ctx` and uses
`ctx.run.id` as the parent run id, so it is fundamentally an
inside-task primitive. Including it on the curated `tasksApi` was a
mistake — with the default `inheritContext: false`, the scoped
taskContext is masked to undefined and the method always throws
"triggerAndSubscribe can only be used from inside a task.run()".

Type test updated to assert the method is no longer reachable from
the instance surface.

Author: ericallam

packages/trigger-sdk/src/v3/triggerClient.ts

@@ -14,18 +14,14 @@ import * as promptsModule from "./prompts.js";
 import * as queuesModule from "./queues.js";
 import { runs } from "./runs.js";
 import * as schedulesModule from "./schedules/index.js";
-import {
-  batchTrigger,
-  trigger,
-  triggerAndSubscribe,
-} from "./shared.js";
+import { batchTrigger, trigger } from "./shared.js";
 
 export type TriggerClientConfig = ApiClientConfiguration & {
   /** Inherit ambient task context (parentRunId, lockToVersion, isTest) when called from inside a task. Default `false`. */
   inheritContext?: boolean;
 };
 
-const tasksApi = { trigger, batchTrigger, triggerAndSubscribe };
+const tasksApi = { trigger, batchTrigger };
 const batchInstanceKeys = ["trigger", "triggerByTask", "retrieve"] as const;
 const schedulesInstanceKeys = [
   "activate",

packages/trigger-sdk/src/v3/triggerClient.types.test.ts

@@ -46,11 +46,13 @@ describe("TriggerClient surface — type-level guarantees", () => {
 describe("TriggerClient surface — curated subsets", () => {
   it("instance.tasks drops inside-task-only and definition-time helpers", () => {
     type Keys = keyof typeof client.tasks;
-    expectTypeOf<Keys>().toEqualTypeOf<"trigger" | "batchTrigger" | "triggerAndSubscribe">();
+    expectTypeOf<Keys>().toEqualTypeOf<"trigger" | "batchTrigger">();
     // @ts-expect-error — triggerAndWait is not on the instance surface.
     client.tasks.triggerAndWait;
     // @ts-expect-error — batchTriggerAndWait is not on the instance surface.
     client.tasks.batchTriggerAndWait;
+    // @ts-expect-error — triggerAndSubscribe requires a task context; not on the instance surface.
+    client.tasks.triggerAndSubscribe;
     // @ts-expect-error — hooks like onStart are task-definition-time, not on the client.
     client.tasks.onStart;
   });