fix: prevent tool parsing within code blocks

[roomote]

Description

This PR fixes issue #8242 where the ask_followup_question tool (and other tools) were incorrectly triggered when displaying code snippets containing tool XML tags.

Problem

When an assistant in Ask mode was asked to describe tool usage and displayed example XML tags in code blocks, the parsing logic incorrectly interpreted these as actual tool invocations rather than code examples.

Solution

Added code block detection to all three message parsing implementations:

• parseAssistantMessage.ts
• parseAssistantMessageV2.ts
• AssistantMessageParser.ts

The parsers now:

1. Track backtick counts to detect code blocks (```) and inline code (`)
2. Maintain state variables (inCodeBlock, inInlineCode) during parsing
3. Skip tool tag processing when inside code blocks
4. Continue accumulating text content normally within code blocks

Testing

• Added 6 comprehensive test cases covering various code block scenarios
• All existing tests continue to pass (73 total tests passing)
• Tests specifically verify the exact issue scenario reported

Changes

• Added code block detection logic to message parsers
• Added comprehensive test coverage for code block handling
• No breaking changes to existing functionality

Fixes #8242

---

Important

Fixes issue #8242 by updating message parsers to prevent tool parsing within code blocks and inline code, with comprehensive tests added.

• Behavior:
  • Fixes issue [BUG] Roo presents the ask_followup_question choice boxes if you ask it to describe how the function works #8242 by preventing tool parsing within code blocks and inline code in parseAssistantMessage.ts, parseAssistantMessageV2.ts, and AssistantMessageParser.ts.
  • Tracks backtick counts to detect code blocks (```) and inline code () and maintains state variables (inCodeBlock`, `inInlineCode`).
  • Skips tool tag processing when inside code blocks or inline code.
• Testing:
  • Adds 6 test cases in parseAssistantMessage.spec.ts to cover various code block scenarios.
  • Ensures all 73 existing tests pass, verifying the exact issue scenario reported.
• Changes:
  • Adds code block detection logic to message parsers.
  • No breaking changes to existing functionality.

^{This description was created by for eb0add2. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

The inline/code block tracking logic is duplicated here. The heuristic toggles inline code on the first non-backtick after a single backtick, which works in the tests but may be fragile in edge cases. Consider explicitly matching a closing backtick and extracting this logic to a shared utility to reduce duplication across parsers.

^{This comment was generated because it violated a code review rule: irule_tTqpIuNs8DV0QFGj.}

[ellipsis-dev]

The variable 'lastTwoChars' is computed but never used. Please remove it to keep the code clean.

[roomote]

Reviewing my own code is like proofreading my own typos - I'll probably miss something obvious.

[roomote]

The lastTwoChars variable is declared on line 19 but never used in the implementation. This appears to be leftover from a different approach and should be removed to avoid confusion.

[roomote]

Consider not toggling inInlineCode when already inside a code block. While the current logic works because inCodeBlock takes precedence, the inInlineCode state could become incorrect:

Suggested change

	inInlineCode = !inInlineCode
	// Check for inline code (single backtick)
	if (codeBlockDelimiterCount === 1 && !inCodeBlock) {
	inInlineCode = !inInlineCode
	}

[roomote]

Same issue here - consider not toggling inInlineCode when already in a code block:

Suggested change

	this.inInlineCode = !this.inInlineCode
	// If we had one backtick and now a different char, toggle inline code
	if (this.codeBlockDelimiterCount === 1 && !this.inCodeBlock) {
	this.inInlineCode = !this.inInlineCode
	}

[roomote]

Same pattern here - only toggle inline code when not in a code block:

Suggested change

	inInlineCode = !inInlineCode
	// If we had one backtick and now a different char, toggle inline code
	if (backtickCount === 1 && !inCodeBlock) {
	inInlineCode = !inInlineCode
	}