chore(python): uncomment ruff version check in python-v2 Dockerfiles

[Swimburger]

Description

Uncomments the RUN ruff --version build-time sanity check in the python-v2 generator Dockerfiles. This check was previously commented out, meaning a broken ruff installation would go undetected until runtime. Enabling it causes the Docker build to fail fast if ruff is not correctly installed or not on PATH.

Changes Made

• Uncommented RUN ruff --version in generators/python-v2/sdk/Dockerfile
• Uncommented RUN ruff --version in generators/python-v2/pydantic-model/Dockerfile

Human Review Checklist

• ⚠️ pydantic-model/Dockerfile will fail to build as-is. The ENV PATH on line 4 is set to /root/.cargo/bin (incorrect), but ruff installs to /root/.local/bin. Uncommenting the version check will cause the build to error because ruff won't be found. This PR should either be merged after the PATH fix PR (fix(python): correct ruff PATH in python-v2/pydantic-model Dockerfile #13871), or the PATH fix should be included here.
• Confirm the sdk/Dockerfile PATH (/root/.local/bin) is correct — this one should work.

Testing

• No Docker build testing performed — verified by code inspection only
• Depends on correct PATH configuration in both Dockerfiles

Link to Devin session: https://app.devin.ai/sessions/371cc6bdbad447bb9161b29b0ab8ec28
Requested by: @Swimburger

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[claude]

⚠️ Code review skipped — your organization's overage spend limit has been reached.

Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit in Settings → Usage.

Once credits are available, reopen this pull request to trigger a review.

[Swimburger]

Is there a reason we shouldn't do this?

[devin-ai-integration]

No reason not to — it's a pure build-time sanity check that catches broken ruff installations before the image ships. The only caveat is that this PR should be merged after #13871 (which fixes the ruff PATH in pydantic-model), otherwise the pydantic-model Docker build will fail because ruff won't be found at the wrong PATH. The sdk Dockerfile already has the correct PATH so it's fine either way.

[devin-ai-integration]

Devin Review found 1 new potential issue.

🐛 1 issue in files not directly in the diff

🐛 types/mod.rs declares modules for inlined types that have no generated file (generators/rust/model/src/generateModels.ts:47-51)

The new computeInlinedUnionVariantTypeIds logic in generateModels.ts:47-51 skips generating .rs files for types in context.inlinedUnionVariantTypeIds. However, ModelGeneratorCli.ts:132-153 (generateTypesModFile) iterates over ALL context.ir.types without checking inlinedUnionVariantTypeIds, so it emits pub mod <inlined_type>; and pub use <inlined_type>::<TypeName>; for types that have no corresponding file. This causes a Rust compilation error (file not found for module). The test snapshot confirms this: types_event_payload.rs is deleted, yet the mod.rs generation code would still declare it.

Same bug also affects SdkGeneratorCli.ts:614

The SDK's buildTypesModule has the identical problem — it iterates all context.ir.types entries without filtering inlined types. Since inlinedUnionVariantTypeIds lives on the temporary ModelGeneratorContext created via toModelGeneratorContext(), the SDK context doesn't even have access to the set.

View 5 additional findings in Devin Review.