Follow PEP8 semantic naming

All identifiers must follow PEP8 naming conventions and clearly convey their intent and scope. Use snake_case for functions and variables—never camelCase—since Python tooling and readers expect PEP8 style (e.g., is_adhoc(value) instead of _isAdHoc(value)). Keep standard conventional names where the language or framework expects them, such as using self as the first parameter of instance methods, even when adding new methods to a mixin or class. Prefix internal helper functions, variables, or attributes that are not part of the public API with a single underscore (e.g., _get_http_code) so users don’t mistakenly treat them as stable, public interfaces. For names that carry semantic meaning external to the code, such as environment variables or configuration flags, choose descriptive names that unambiguously state their purpose and scope—for example, prefer FLASK_RUN_FROM_CLI over a vaguer FLASK_RUN_FROM_APP_RUN if the variable is only ever meant to be set by the CLI. When in doubt, prioritize clarity and consistency with existing codebase/language conventions over introducing new or unconventional naming patterns.