Problem

Fixes false positive 'stuck in a loop' error for native protocol tools like read_file that store parameters in nativeArgs instead of params.

Previously, the ToolRepetitionDetector only compared the params object, which was empty for native protocol tools. This caused all read_file calls to appear identical, triggering false loop detection even when reading different files.

Root Cause

1. In NativeToolCallParser.ts: For native protocol, the files parameter (an array) is intentionally NOT added to the legacy params object since it can't be meaningfully stringified. Instead, it's stored in nativeArgs.
2. In ToolRepetitionDetector.ts: The serializeToolUse() method only looked at toolUse.params to compare tools, completely ignoring nativeArgs.

Result: Every read_file call serialized to {"name":"read_file","parameters":{}} regardless of which files were being read.

Solution

Updated ToolRepetitionDetector.serializeToolUse() to also include nativeArgs in the serialization when present. Now read_file calls with different files are properly differentiated while still detecting true repetitions.

Changes

• Updated serializeToolUse() method to include nativeArgs in comparison
• Added comprehensive tests for native protocol scenarios
• Maintains backward compatibility with XML protocol tools that don't have nativeArgs

Testing

• Added 5 new test cases covering native protocol scenarios
• All 32 tests in ToolRepetitionDetector.spec.ts pass
• Verified different files are treated as different calls
• Ensures identical calls are still detected as repetitions

Closes: Issue reported in Discord about read_file loop detection