Clerifications: My ticket is specifically about the Python Admin API wrapper splitapiclient, not the Python SDK. The issue description includes the exact endpoint PATCH /internal/api/v2/splits/ws/{workspace-id}/{feature-flag-name}, references to the API documentation, the current method gap in SplitMicroClient, and a proposed implementation for adding support.

I'm aware that we can call the API directly, that's always an option with any HTTP API. But the purpose of having an official API wrapper is to avoid that. Making raw HTTP calls means we lose the consistent auth handling, response parsing, and resource abstractions that splitapiclient provides. It also means every consumer has to reimplement those concerns individually.

Given that the wrapper already exposes most CRUD operations on splits (get, list, add, delete, update_description, associate_tags), adding the PATCH endpoint would be a straightforward incremental addition and the proposed implementation is included in the ticket.

Regarding priority, I'd prefer to keep it as is. While there is a workaround, the whole value of the wrapper is that teams shouldn't need workarounds for supported API endpoints.