EPIC: Python API Experience

Outcome: A consistently discoverable, well-documented, and Pythonic API.

2026 Deliverables
- Meaningful help text on every public API item #4736 #4737
- 100% type hints backed up by full support for runtime type-checking #4738 #4739
- Improved exposure of settings enum types: better discoverability through more expressive API and proper integration with API reference #4733
- VariableDescriptors: ensure comprehensive variable coverage and add vector/scalar typing for API safety #4740 #4742 [pyansys-units#443](https://github.com/ansys/pyansys-units/issues/443)
- Complete redesign of the API reference: #4741
- Organized primarily by objects the user interacts with
- Class/type reference remains available but de-emphasized
- Significantly improved readability and navigation
- Expanded library of curated, real-world examples in close partnership with ACE
- Refine PyFluent’s Settings API exposure process, enforcing quality thresholds that increase with each release

Start by reviewing the linked deliverable issues #4736–#4742 and the pyansys-units issue #443 to identify a discrete contribution. The epic covers API help text, type hints, enum exposure, VariableDescriptors, API reference redesign, examples, and release quality thresholds. Done means the relevant child deliverable is completed and its stated API-experience outcome is met.

Written by the indexing model from the issue text.