33 Refactor Without Breaking Behavior
34 Refactor Without Breaking Behavior
34.1 Weak Request
Clean up this Python module and make it nicer.
34.2 Repaired Spell
ROLE: Act as a senior Python engineer performing behavior-preserving refactoring.
OBJECTIVE: Remove duplication in the supplied module without changing public behavior.
CONTEXT: The module is imported by two API handlers and one CLI entry point. Existing tests cover only the happy path.
CONSTRAINTS: Do not change public function names, parameter order, return types, or raised exception classes. Touch only this module and its tests.
OUTPUT CONTRACT: Return a minimal patch plan, the proposed refactor, and tests that prove unchanged behavior.
VERIFICATION: State the invariants first; then show before/after test cases for edge inputs.
FAILURE BEHAVIOR: If the module boundary is too small for a safe refactor, say exactly what adjacent file must also move and why.34.3 Expected Delta
The repaired spell narrows blast radius, makes invariants reviewable, and forces proof through tests instead of relying on claims of cleanliness.