Greptile Summary

• Changed MutableProxy.__getattr__ to stop wrapping method return values, fixing issue where copying dataclass/model instances incorrectly marked state as dirty
• Added comprehensive tests verifying that copies of mutable objects can be modified without affecting the original state's dirty tracking

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is well-targeted and fixes a legitimate bug where method return values were incorrectly wrapped in MutableProxy. The fix correctly distinguishes between methods that mutate self (still tracked via proxy binding) and methods that return new instances (no longer wrapped). Comprehensive tests verify both the fix and that existing behavior is preserved.
• No files require special attention

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant State
    participant MutableProxy
    participant Method
    participant DataClass
    
    User->>State: Access `state.dc.copy()`
    State->>MutableProxy: `__getattr__("copy")`
    MutableProxy->>MutableProxy: Detect method with `__func__`
    MutableProxy->>Method: Rebind self using `functools.partial`
    Method->>DataClass: Call `dataclasses.replace(self, **kwargs)`
    DataClass-->>Method: Return new DataClass instance (unwrapped)
    Method-->>User: Return new instance
    User->>DataClass: Modify copy with `dc_copy.foo = "new"`
    Note over State: State remains clean (no dirty vars marked)

CodSpeed Performance Report

Merging #5986 will not alter performance

_{Comparing masenf/mutable-proxy-methods2 (5a47690) with main (4ee713f)}

Summary

✅ 8 untouched