SDK regeneration

[fern-api]

Automated SDK generation by Fern

---

✅ Customizations automatically preserved, but 16 files need your attention.

Action required: 16 files with unresolved customization conflicts

The new generation changed code you previously customized. Non-conflicting customizations have been applied automatically. The following files need manual resolution:

File	Your customization	Why it conflicted
reference.md	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	The new generation changed the same lines you edited
src/smallestai/atoms/__init__.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	The new generation changed the same lines you edited
src/smallestai/atoms/agent_telephony/raw_client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	The new generation changed the same lines you edited
src/smallestai/atoms/client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	The new generation changed the same lines you edited
src/smallestai/waves/ops/raw_client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	The new generation changed the same lines you edited
src/smallestai/waves/analytics/__init__.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	Both the generator and your customization created this file
src/smallestai/waves/analytics/client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	Both the generator and your customization created this file
src/smallestai/waves/analytics/raw_client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	Both the generator and your customization created this file
src/smallestai/waves/analytics/types/__init__.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	Both the generator and your customization created this file
src/smallestai/waves/client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	The new generation changed the same lines you edited
src/smallestai/waves/ops/raw_client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	Both the generator and your customization created this file
src/smallestai/waves/post_call_analysis/client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	Both the generator and your customization created this file
src/smallestai/waves/post_call_analysis/raw_client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	Both the generator and your customization created this file
src/smallestai/waves/voices/client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	Both the generator and your customization created this file
src/smallestai/waves/voices/raw_client.py	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	The new generation changed the same lines you edited
wiremock/wiremock-mappings.json	release: 5.10.0 — adapters, tools, crew ownership, telemetry, CLI DevX (#95)	The new generation changed the same lines you edited

How to resolve

1. Check out this branch:

   git fetch origin && git checkout -b fern-bot/2026-09-24_14-28-02_263 origin/fern-bot/2026-09-24_14-28-02_263

   Or if you don't have the repo cloned:

   git clone https://github.com/smallest-inc/smallest-python-sdk.git && cd smallest-python-sdk && git checkout -b fern-bot/2026-09-24_14-28-02_263 origin/fern-bot/2026-09-24_14-28-02_263

2. Run: fern replay resolve
3. Open the conflicting files in your editor — you'll see standard merge conflict markers
4. Resolve using your editor's merge tools (VS Code, IntelliJ, etc.)
5. Run: fern replay resolve again to finalize
6. Push your changes

Your resolved customizations will be remembered on future SDK generations.
If you merge this PR without resolving, your unresolved customizations will conflict again on the next generation.

[crim-app]

crim doesn't review pull requests automatically here.

Comment crim review on this pull request whenever you want a review.

[abhishekmishragithub]

Holding this as a draft — CI is red from spec-side regressions on main, not the telephony work. Verified locally:

mypy (15 errors, 3 files)

• exportCampaignResultsByAudienceMember and exportCampaignLogs have no x-fern-sdk-group-name in fern/apis/atoms/openapi/openapi.yaml, so Fern misfiles them into atoms/agent_telephony/raw_client.py without importing ExportCampaignResultsByAudienceMember{RequestFormat,Response}. In 5.12.2 they were correctly in atoms/campaigns. Fix: add x-fern-sdk-group-name: campaigns to both operations.
• get_subscription_user (new) generates into waves/ops/raw_client.py referencing GetSubscriptionUserResponse/UnauthorizedError/InternalServerError that aren't imported — its response + error schemas need wiring in the waves spec.

ruff (38) — waves/types/__init__.py imports CatalogVoice, CatalogVoiceTags, etc. twice (duplicate type surfaced by two waves sub-specs) → F811/F601.

gitleaks (4) — example tokens in generated files; needs an allowlist entry in .gitleaks.toml.

The telephony surface itself (sip_trunks, agent_telephony caller-id/answer binding, outbound from_number/from_product_id) is correct and was live-verified (real outbound call placed via this SDK). Fix path: correct the spec grouping + the new subscription/catalog types in smallest-ai-documentation, re-regen, confirm all four gates green, then take 5.13.0 out of draft.

[abhishekmishragithub]

Superseded by #127, regenerated off the fixed atoms spec (PRO-3262 / docs #479). #127 has the same telephony surface with the campaign group-name fix, so it should pass CI.