refactor: replace stream-json with sax parser for message parsing

- Remove stream-json and proper-lockfile dependencies
- Add sax parser dependency
- Refactor DirectiveStreamingParser to use SAX parser
- Reorganize assistant-message module to message-parsing
- Extract directive parsing into focused classes
- Update all related tests and imports
- Maintain backward compatibility with existing API

Author: daniel-lxs

.github/pull_request_template.md

@@ -38,15 +38,37 @@ Detail the steps to test your changes. This helps reviewers verify your work.
 - Include relevant testing environment details if applicable.
 -->
 
+### Type of Change
+
+<!-- Mark all applicable boxes with an 'x'. -->
+
+- [ ] 🐛 **Bug Fix**: Non-breaking change that fixes an issue.
+- [ ] ✨ **New Feature**: Non-breaking change that adds functionality.
+- [ ] 💥 **Breaking Change**: Fix or feature that would cause existing functionality to not work as expected.
+- [ ] ♻️ **Refactor**: Code change that neither fixes a bug nor adds a feature.
+- [ ] 💅 **Style**: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
+- [ ] 📚 **Documentation**: Updates to documentation files.
+- [ ] ⚙️ **Build/CI**: Changes to the build process or CI configuration.
+- [ ] 🧹 **Chore**: Other changes that don't modify `src` or test files.
+
 ### Pre-Submission Checklist
 
 <!-- Go through this checklist before marking your PR as ready for review. -->
 
 - [ ] **Issue Linked**: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
 - [ ] **Scope**: My changes are focused on the linked issue (one major feature/fix per PR).
 - [ ] **Self-Review**: I have performed a thorough self-review of my code.
-- [ ] **Testing**: New and/or updated tests have been added to cover my changes (if applicable).
+- [ ] **Code Quality**:
+    - [ ] My code adheres to the project's style guidelines.
+    - [ ] There are no new linting errors or warnings (`npm run lint`).
+    - [ ] All debug code (e.g., `console.log`) has been removed.
+- [ ] **Testing**:
+    - [ ] New and/or updated tests have been added to cover my changes.
+    - [ ] All tests pass locally (`npm test`).
+    - [ ] The application builds successfully with my changes.
+- [ ] **Branch Hygiene**: My branch is up-to-date (rebased) with the `main` branch.
 - [ ] **Documentation Impact**: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
+- [ ] **Changeset**: A changeset has been created using `npm run changeset` if this PR includes user-facing changes or dependency updates.
 - [ ] **Contribution Guidelines**: I have read and agree to the [Contributor Guidelines](/CONTRIBUTING.md).
 
 ### Screenshots / Videos

.roo/rules-code/use-safeWriteJson.md

@@ -64,10 +64,8 @@
     1. Identify where the string appears in the UI/codebase
     2. Understand the context and purpose of the string
     3. Update English translation first
-    4. Use the `<search_files>` tool to find JSON keys that are near new keys in English translations but do not yet exist in the other language files for `<apply_diff>` SEARCH context
-    5. Create appropriate translations for all other supported languages utilizing the `search_files` result using `<apply_diff>` without reading every file.
-    6. Do not output the translated text into the chat, just modify the files.
-    7. Validate your changes with the missing translations script
+    4. Create appropriate translations for all other supported languages
+    5. Validate your changes with the missing translations script
 - Flag or comment if an English source string is incomplete ("please see this...") to avoid truncated or unclear translations
 - For UI elements, distinguish between:
     - Button labels: Use short imperative commands ("Save", "Cancel")

.roo/rules-translate/001-general-rules.md

@@ -25,8 +25,6 @@ customModes:
         - fileRegex: (\.roomodes$|\.roo/.*\.xml$|\.yaml$)
           description: Mode configuration files and XML instructions
       - command
-      - mcp
-    source: project
   - slug: test
     name: 🧪 Test
     roleDefinition: |-
@@ -205,55 +203,3 @@ customModes:
           description: Temporary documentation extraction files only
       - command
       - mcp
-  - slug: pr-fixer
-    name: 🛠️ PR Fixer
-    roleDefinition: "You are Roo, a pull request resolution specialist. Your focus is on addressing feedback and resolving issues within existing pull requests. Your expertise includes: - Analyzing PR review comments to understand required changes. - Checking CI/CD workflow statuses to identify failing tests. - Fetching and analyzing test logs to diagnose failures. - Identifying and resolving merge conflicts. - Guiding the user through the resolution process."
-    whenToUse: Use this mode to fix pull requests. It can analyze PR feedback from GitHub, check for failing tests, and help resolve merge conflicts before applying the necessary code changes.
-    description: Fix pull requests.
-    groups:
-      - read
-      - edit
-      - command
-      - mcp
-  - slug: issue-investigator
-    name: 🕵️ Issue Investigator
-    roleDefinition: You are Roo, a GitHub issue investigator. Your purpose is to analyze GitHub issues, investigate the probable causes using extensive codebase searches, and propose well-reasoned, theoretical solutions. You methodically track your investigation using a todo list, attempting to disprove initial theories to ensure a thorough analysis. Your final output is a human-like, conversational comment for the GitHub issue.
-    whenToUse: Use this mode when you need to investigate a GitHub issue to understand its root cause and propose a solution. This mode is ideal for triaging issues, providing initial analysis, and suggesting fixes before implementation begins. It uses the `gh` CLI for issue interaction.
-    description: Investigates GitHub issues
-    groups:
-      - read
-      - command
-      - mcp
-    source: project
-  - slug: merge-resolver
-    name: 🔀 Merge Resolver
-    roleDefinition: |-
-      You are Roo, a merge conflict resolution specialist with expertise in:
-      - Analyzing pull request merge conflicts using git blame and commit history
-      - Understanding code intent through commit messages and diffs
-      - Making intelligent decisions about which changes to keep, merge, or discard
-      - Using git commands and GitHub CLI to gather context
-      - Resolving conflicts based on commit metadata and code semantics
-      - Prioritizing changes based on intent (bugfix vs feature vs refactor)
-      - Combining non-conflicting changes when appropriate
-
-      You receive a PR number (e.g., "#123") and:
-      - Fetch PR information including title and description for context
-      - Identify and analyze merge conflicts in the working directory
-      - Use git blame to understand the history of conflicting lines
-      - Examine commit messages and diffs to infer developer intent
-      - Apply intelligent resolution strategies based on the analysis
-      - Stage resolved files and prepare them for commit
-    whenToUse: |-
-      Use this mode when you need to resolve merge conflicts for a specific pull request.
-      This mode is triggered by providing a PR number (e.g., "#123") and will analyze
-      the conflicts using git history and commit context to make intelligent resolution
-      decisions. It's ideal for complex merges where understanding the intent behind
-      changes is crucial for proper conflict resolution.
-    description: Resolve merge conflicts intelligently using git history.
-    groups:
-      - read
-      - edit
-      - command
-      - mcp
-    source: project

.roomodes

@@ -277,6 +277,7 @@
 - Fix context length for lmstudio and ollama (thanks @thecolorblue!)
 - Resolve MCP tool eye icon state and hide in chat context (thanks @daniel-lxs!)
 
+=======
 ## [3.21.2] - 2025-06-20
 
 - Add LaTeX math equation rendering in chat window

CHANGELOG.md

@@ -767,7 +767,7 @@ suite.skip("Roo Code use_mcp_tool Tool", function () {
 		}
 	})
 
-	test.skip("Should validate MCP request message format and complete successfully", async function () {
+	test("Should validate MCP request message format and complete successfully", async function () {
 		const api = globalThis.api
 		const messages: ClineMessage[] = []
 		let _taskCompleted = false