Stainless-Generated-From: a36f24499537e73356c6d97d2f2864fd9765287d

Stainless-Generated-From: 0105c17d76d19161783d9d232bc294570f913919

Two-repo fast-forward core from the stlc sdk-repo example, with the
placeholders pointed at this pair:

  staging     runloopai/api-client-python-staging
  production  runloopai/api-client-python
  config      runloopai/runloop

Both files self-route with if: github.repository == ... guards, so the same
two files serve staging and production and only the right jobs run in each.
They reach production via the first promote.

Sealed as custom code so they survive regeneration.

Stainless-Generated-From: 9d629f617c9ec875f51e803415969e636ac2cc8b

Both SDKs are at a stable 1.30.0, but the scaffolded release-please-config.json
still carried the prerelease strategy, which would cut 1.31.0-alpha.1 on the
first stock release-please run.

  versioning: prerelease -> default   (the field that adds the -alpha.N suffix)
  prerelease: true -> false           (marks the GitHub Release as a prerelease)

Both values verified against googleapis/release-please's published config
schema: versioning "defaults to `default`", prerelease is "create the GitHub
release as prerelease".

Hand-edited rather than configured: publish.release.prerelease: false in
stainless.yml does not reach this file. stlc scaffolds it once and preserves it
thereafter, and --rewrite-scaffold does not refresh it — with the file deleted
and --rewrite-scaffold passed, stlc did not recreate it at all. Preserved
scaffold is the documented place for hand-edits to survive.

Empty by design. The generated code for POST /v1/devboxes/{id}/create_gateway_token
is already on this branch — it arrived via 9591d74 ("initial stlc build"), which
regenerated the whole SDK from a spec that already contained the endpoint.

This commit exists only to restore changelog attribution. The cloud pipeline
recorded this feature as b7763ba on the now-abandoned `next` branch, and
release-please reads commit messages rather than diffs, so without it the 1.31.0
changelog credits the API addition to a "Build SDK" commit instead.

Empty by design. The generated code for POST /v1/devboxes/{id}/create_mcp_token
is already on this branch — it arrived via 9591d74 ("initial stlc build"), which
regenerated the whole SDK from a spec that already contained the endpoint.

This commit exists only to restore changelog attribution. The cloud pipeline
recorded this feature as a02b75f on the now-abandoned `next` branch, and
release-please reads commit messages rather than diffs, so without it the 1.31.0
changelog credits the API addition to a "Build SDK" commit instead.

The generated tree and the custom code each added an import at the same line,
so integrating them left `...lib.wait_for_status` inside the `...types.*` block
and ruff's isort rule (I001) rejected it. Both symbols are used, so the
resolution keeps both and only reorders.

Applied by ./scripts/format rather than by hand, so the ordering is whatever
ruff wants rather than whatever looked right.