Python Docstring Enhancer

Document the behavior a reader cannot reliably infer from names, types, and code structure. Preserve runtime behavior and the repository's existing docstring convention.

Quick Start

1. Read repository instructions, the target Python, neighboring documented code, and docstring/lint configuration such as pyproject.toml.
2. Identify public surfaces and non-obvious behavior in the requested scope.
3. Add the smallest docstrings or comments that explain the contract, rationale, invariant, side effect, or failure behavior.
4. Do not change executable code, signatures, annotations, or formatting beyond what the documentation edit requires unless the user requested a refactor.
5. Parse the changed files and run the repository's focused documentation, lint, type, or test checks when available.

What Deserves Documentation