feat: add translation workflow to issue-fixer mode

[hannesrudolph]

Description

This PR enhances the issue-fixer mode by integrating a translation workflow step to ensure all user-facing content changes are properly localized.

Changes Made

• Added Step 7 "Check for Translation Requirements" to the issue-fixer workflow in .roo/rules-issue-fixer/1_Workflow.xml

  • Analyzes implementation for new user-facing strings, error messages, and documentation
  • Automatically delegates translation tasks to translate mode when needed
  • Ensures translations are completed before final testing

• Updated best practices in .roo/rules-issue-fixer/2_best_practices.xml

  • Added guidelines for delegating translation tasks
  • Emphasized checking for hard-coded strings and i18n needs
  • Added note to wait for translation completion before final testing

Why This Change?

When fixing issues or implementing features, developers often introduce new user-facing content that needs to be translated into all supported languages. This workflow enhancement ensures that:

1. Translation requirements are identified systematically
2. No user-facing content is left untranslated
3. The translation process is integrated seamlessly into the issue-fixing workflow
4. All supported languages remain in sync

Testing

The workflow has been designed to:

• Check for translation needs after implementation (Step 7)
• Create detailed translation tasks with proper context
• Wait for translation completion before proceeding to final tests

Checklist

• Code follows project style guidelines
• Self-review completed
• Comments added for complex logic
• Documentation updated
• No breaking changes

---

Important

Adds a translation workflow step to issue-fixer mode, ensuring user-facing content is localized before final testing.

• Workflow Changes:
  • Adds Step 7 "Check for Translation Requirements" in 1_Workflow.xml to identify and delegate translation tasks for new user-facing content.
  • Ensures translations are completed before final testing.
• Best Practices:
  • Updates 2_best_practices.xml to include guidelines for delegating translation tasks and checking for hard-coded strings.
  • Emphasizes waiting for translation completion before final testing.

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

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to ada6924.

Security Overview

• 🔎 Scanned files: 2 changed file(s)

Detected Code Changes

Change Type	Relevant files
Enhancement	► 1_Workflow.xml     Added translation workflow step     Updated step numbering sequence ► 2_best_practices.xml     Added translation-related best practices

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

[Copilot]

Pull Request Overview

This PR integrates a translation workflow into the issue-fixer mode and updates related best practices.

• Inserts a new Step 7 in the workflow to detect and delegate translation tasks.
• Renumbers subsequent steps (8→9, 9→10, 10→11, 11→12).
• Adds translation and i18n checks to the best practices document.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.roo/rules-issue-fixer/1_Workflow.xml	Added “Check for Translation Requirements” as Step 7 and renumbered later steps
.roo/rules-issue-fixer/2_best_practices.xml	Added guidelines on delegating translation tasks and checking hard-coded strings

Comments suppressed due to low confidence (3)

.roo/rules-issue-fixer/1_Workflow.xml:287

• [nitpick] The bracketed placeholder could be confusing if left literal; consider clarifying that this is a template field or provide an example to guide users.

       - [List specific files and what content needs translation]

.roo/rules-issue-fixer/2_best_practices.xml:15

• [nitpick] Indentation is inconsistent with the existing bullet list; align this item to match the four-space indent of the other list entries.

  - Delegate translation tasks to translate mode when implementing user-facing changes

.roo/rules-issue-fixer/1_Workflow.xml:310

• [nitpick] This tag is indented differently than neighboring steps; adjust its indentation level to stay consistent with the surrounding XML structure.

   <step number="8">