feat: add Fern-generated Python SDK alongside TypeScript

[bhaveshpatel640]

Summary

Add Fern-generated Python SDK (packages/trueforge-python-sdk) next to the TypeScript SDK, and wire CI to regenerate/commit it

Closes AGE-2005

Changes

• Fern python-sdk group (local-file-system) + pnpm sdk:generate / Generate SDK workflow
• Bootstrap pyproject.toml (0.1.0-rc.1) + .fernignore

How was this tested?

• fern generate --group python-sdk locally; optional_auth / version stamp checked
• Workflow path review (no full CI run in this session)

Checklist

• I have read the contributing guidelines
• pnpm build, pnpm test, pnpm typecheck, pnpm lint:ci, and pnpm format:check pass locally
• Tests added/updated where it makes sense
• No hand-edits to generated code (packages/trueforge-sdk, packages/trueforge-python-sdk, .github/fern/openapi/openapi.json, docs/openapi.json) — fork PRs must commit pnpm sdk:generate output (CI cannot push to forks)
• Docs / .env.example updated if configuration or behavior changed

---

Note

Low Risk
Changes are limited to SDK generation config, CI commit paths, and checked-in generated client code—no server or auth runtime logic.

Overview
Adds a Fern python-sdk generator that writes to python/trueforge_sdk (local filesystem), mirroring the existing TypeScript SDK setup with optional auth, streaming, and TrueForge / AsyncTrueForge clients.

The Generate SDK workflow and Fern config now treat Python as a first-class generated artifact: path filters include scripts/generate-sdk.sh, regen triggers when that script changes, and bot commits add python/trueforge_sdk alongside OpenAPI and packages/trueforge-sdk. Changesets still run only for the TypeScript package; fork-PR messaging warns not to hand-edit the Python tree.

This PR also checks in the initial generated SDK (clients, types, README/reference docs, minimal pyproject.toml at 0.1.0-rc.1, .fernignore for custom pyproject.toml).

^{Reviewed by Cursor Bugbot for commit 5c26533. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5c26533

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 5c26533. Configure here.}

[cursor]

Python SDK package metadata is incomplete

Medium Severity

pyproject.toml only declares Poetry name, version, and description, and .fernignore keeps Fern from replacing it. The file has no [build-system], dependencies, or src/ package map, so pip install / poetry install cannot build or import trueforge_sdk. generators.yml settings such as pyproject_python_version never land in the committed project file.

Additional Locations (1)

• python/trueforge_sdk/.fernignore#L1-L2

 

^{Reviewed by Cursor Bugbot for commit 5c26533. Configure here.}

[cursor]

Generated Python SDK not Prettier-ignored

Medium Severity

format:check globs all *.md and *.json, and .prettierignore only excludes packages/trueforge-sdk/. The new python/trueforge_sdk README, 4k-line reference.md, and .fern/metadata.json are now linted. Fern will rewrite them on the next sdk:generate, so a local format fix will not stick and CI can fail after every regen.

Additional Locations (2)

• python/trueforge_sdk/reference.md#L1-L50
• python/trueforge_sdk/.fern/metadata.json#L1-L29

 

^{Reviewed by Cursor Bugbot for commit 5c26533. Configure here.}