Method triggerRunWithMeta

src/lib/http.ts:262–276

* Like `triggerRun` but returns the full `RequestResult` so the caller * can surface the `requestId` in happy-path CLI output. * * `retryOnRateLimit` defaults to `true` so single `test run` and * `test create --run` retain the standard HTTP-layer 429 retry budget. * * Pass `retryOn

(
    testId: string,
    body: TriggerRunBody,
    options: { idempotencyKey: string; signal?: AbortSignal; retryOnRateLimit?: boolean },
  )

   * extra retries per outer attempt, which would multiply POSTs per spec (e.g. 50×3 = 150/min).
   */
  async triggerRunWithMeta(
    testId: string,
    body: TriggerRunBody,
    options: { idempotencyKey: string; signal?: AbortSignal; retryOnRateLimit?: boolean },
  ): Promise<RequestResult<TriggerRunResponse>> {
    return this.postWithMeta<TriggerRunResponse>(`/tests/${encodeURIComponent(testId)}/runs`, {
      body,
      headers: { 'idempotency-key': options.idempotencyKey },
      signal: options.signal,
      retryOnConflict: false,
      // Default true: single `test run` / `test create --run` retain 429 retry.
      // Batch call site passes false to keep outer-loop as sole rate-limit owner.
      retryOnRateLimit: options.retryOnRateLimit ?? true,
    });
  }

  /**
   * POST /api/cli/v1/tests/{testId}/runs/rerun