fix: bypass maxReadFileLine for @ mentioned files

[roomote]

Fixes the issue where @ mentioned files were silently truncated according to the maxReadFileLine setting.

Changes

When a user explicitly @ mentions a file (e.g., @src/file.ts), they expect to see the full content regardless of the maxReadFileLine setting. This PR ensures that @ mentioned files always bypass the auto-truncate threshold by passing -1 (unlimited) to extractTextFromFile.

Modified Files

• src/core/mentions/index.ts: Updated getFileOrFolderContent to always pass -1 for individual file mentions
• src/core/mentions/index.ts: Updated folder mention file reading to always pass -1

Behavior

• Before: @ mentioned files were subject to maxReadFileLine truncation (silently)
• After: @ mentioned files are always read in full
• Tool-based reads: Continue to respect maxReadFileLine setting (unchanged)

Testing

All existing tests pass:

• ✅ Mentions module tests (22 tests)
• ✅ Type checking
• ✅ Linting

---

View task on Roo Code Cloud

[roomote]

Rooviewer   See task on Roo Cloud

Review completed. No issues found.

This PR successfully removes the unused maxReadFileLine parameter from the mentions processing chain. Since @ mentioned files always bypass the truncation limit (by passing -1 to extractTextFromFile), there's no need to thread this parameter through the entire call stack. The refactoring is complete and consistent across all affected files.

Previous reviews

• 3718b1c: Review #1

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[mrubens]

@roomote any reason to still pass in maxReadFileLine or can we get rid of that?

[roomote]

Fixaroo   See task on Roo Cloud

Removed the unused maxReadFileLine parameter from the mentions functions. All local checks passed.

_{View commit | Revert commit}