feat(condense v2.1): add smart code folding

[hannesrudolph]

Thank you @shariqriazz for this idea. (make sure to include this thank you in the change log and the release notes)

What This Does For You

When Roo condenses a long conversation, it now preserves a lightweight map of the files you worked on—function signatures, class declarations, type definitions—so it can continue referencing them accurately after condensing.

File Selection & Budget

Budget: ~50,000 characters total for folded file context.

Order: Files are included most recently read first. If the budget runs out, older files (read earlier in the task) are omitted—your most recent work is always preserved.

Scope: Only files Roo actually read (via tools or mentions) are included. Files you edited outside Roo, or files in the project Roo never saw, are not included.

How It Works

1. Roo gathers files it read during the task, sorted by most recent first.
2. For each file, it extracts structural definitions (signatures, declarations) using tree-sitter—no implementation bodies.
3. Each file is wrapped in a <system-reminder> block and appended to the condensed summary.
4. Processing stops when the 50k character budget is reached.

What You'll See

After condensing, the summary includes lightweight code outlines:

## File Context: src/api.ts
# api.ts
1--10 | export async function fetchData(url: string): Promise<Response>
12--45 | export class ApiClient

Benefits

• Better continuity: Roo knows what exists in files it read, even after the original messages are summarized away.
• Smarter edits: When you say "update that function," Roo still knows its shape.
• No action required: This happens automatically—you don't need to re-share files.

Limitations

• Budget cap: Very large codebases may have older files omitted.
• Supported languages only: File types without tree-sitter support are skipped.
• Read files only: Files Roo never saw are not included.

Technical Summary

• getFilesReadByRoo() returns files sorted by most recent read timestamp
• generateFoldedFileContext() extracts definitions via tree-sitter with a 50k char budget
• Integrated into summarizeConversation() during context condensation
• Each file gets its own <system-reminder> block for high-priority retention

[roomote]

Oroocle   See task on Roo Cloud

Re-review complete. No new issues found.

• Add smart code folding / PR feat(condense v2.1): add smart code folding #10942 to the release notes surfaces (changelog + in-app announcement if applicable), including the requested thanks to @shariqriazz.

Previous reviews

• 5b3cb96: Review #1
• 697022d: Review #2
• 8834ffe: Review #3
• 9a16603: Review #4
• 1b12051: Review #5
• 8fbaee2: Review #6
• 9ecf7b4: Review #7
• 66d2d30: Review #8
• f4c395b: Review #9
• cccc2ff: Review #10
• 21cda01: Review #11

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

[roomote]

Fixaroo   See task on Roo Cloud

Fixed the reported issue. Tree-sitter error strings are now skipped instead of embedded in folded file context. All local checks passed.

_{View commit | Revert commit}

[daniel-lxs]

Looks good!

-Sent from Dan's agent

[daniel-lxs]

One concern - did you test or research if all providers handle multiple text blocks in a single message content array properly? Some providers might have issues with this structure.

[hannesrudolph]

One concern - did you test or research if all providers handle multiple text blocks in a single message content array properly? Some providers might have issues with this structure or flatten it differently than expected.

I verified this works correctly. For user messages (which the summary is), the format converter preserves the array structure:

content: [
  { type: "text", text: "Summary..." },
  { type: "text", text: "<system-reminder>..." },
  { type: "text", text: "<system-reminder>..." }
]

The .join("\n") behavior only applies to assistant messages. All providers properly receive multiple text blocks in user messages.