feat(condense): add smart code folding with tree-sitter signatures

[hannesrudolph]

Summary

At context condensation time, this PR uses tree-sitter to generate folded code signatures (function definitions, class declarations, etc.) for files that were read during the conversation. Each file is included as its own <system-reminder> block in the condensed summary, preserving structural awareness without consuming excessive tokens.

This allows the model to retain awareness of file structure after condensing, enabling better continuity when working with codebases.

File Selection Behavior

Files accumulate across multiple condensing events within a task:

• Read files A, B, C → Condense Add options to always approve write and execute operations #1 → Summary includes folded context for A, B, C
• Read files D, E, F → Condense Fix vscode compatibility issue #2 → Summary includes folded context for A, B, C, D, E, F

This is because files_in_context metadata is persisted to disk via saveTaskMetadata(). The getFilesReadByRoo() method queries all files ever read during the task lifetime, not just since the last condense.

File sources included:

• read_tool - Files explicitly read by the agent
• file_mentioned - Files mentioned/referenced in conversation

Changes

• FileContextTracker: Added getFilesReadByRoo() method to query files read during the task (filters by read_tool and file_mentioned sources)

• foldedFileContext.ts (new file):

  • generateFoldedFileContext() function using tree-sitter parsing
  • Returns both content (joined string) and sections (array of individual file blocks)
  • Each file wrapped in its own <system-reminder> block
  • Character budget handling for large codebases (default 50,000 chars)

• index.ts (condense): Updated summarizeConversation() to accept foldedFileContextSections?: string[] and push each section as a separate content block in the summary message

• Task.ts: Integrated smart code folding in condenseContext() - calls generateFoldedFileContext() and passes sections to summarizeConversation()

• Tests: 12 comprehensive tests covering:

  • Empty file list handling
  • Single/multiple file generation
  • Separate system-reminder blocks per file
  • Character budget limits
  • Error handling for unsupported files

Output Format

Each file gets its own content block in the summary message:

// Summary message content array:
[
  { type: "text", text: "## Conversation Summary\n..." },
  { type: "text", text: "<system-reminder>\n## File Context: src/api.ts\n...\n</system-reminder>" },
  { type: "text", text: "<system-reminder>\n## File Context: src/models.ts\n...\n</system-reminder>" },
]

[roomote]

Oroocle   See task on Roo Cloud

Re-review complete. The previously flagged tree-sitter error-string embedding issue is resolved in the latest commit.

• Avoid embedding tree-sitter error strings into folded file context (treat missing/denied files as skipped instead).

Previous reviews

• 21cda01: Review #1

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

[roomote]

parseSourceCodeDefinitionsForFile() can return human-readable error strings (for example when a file is missing). Since those are truthy, generateFoldedFileContext() will embed the error text into the condensed context as if it were a code signature; it seems better to treat these as a skip (undefined/null) so condensation does not preserve error messages.

_{Fix it with Roo Code or mention @roomote and request a fix.}

[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}