docs: v3.28.3 release notes and v3.28 combined sync\n\n- Add v3.28.3 patch notes and align combined v3.28 notes\n- Correct keyboard shortcut docs (roo-cline.* IDs; Add to Context Cmd+Y/Ctrl+Y; focus note)\n- Update Auto-Approve docs to match new UI (Enabled toggle position, All/None chips)\n- Add Z.ai region-aware plan details; ByteString troubleshooting; related doc tweaks\n- Keep index and sidebar in sync (#344)

Author: hannesrudolph

.roo/rules-release-notes-writer/1_main_workflow.xml

@@ -108,11 +108,12 @@ gh pr list --repo RooCodeInc/Roo-Code --state merged --base main --limit 1000 \
         <details>
           Parent task MUST create this file (and .roo/tmp/release-notes/temp_pr_inclusion_v[version].json, .roo/tmp/release-notes/temp_pr_list_v[VERSION].md if needed) before ANY subtasks.
           Subtasks will ONLY append using insert_content.
+          Parent task MUST NOT append to temp_pr_analysis_v[version].md; this file is reserved exclusively for subtask outputs. The parent may only create/initialize the empty file(s).
           Temp files live under .roo/tmp/release-notes/
         </details>
       </initialization>
 
-      <subtask_pattern>
+      <subtask_pattern priority="CRITICAL">
         <for_each>PR in list</for_each>
         <action>Create investigation subtask using new_task tool</action>
         <implementation>
@@ -128,22 +129,23 @@ gh pr list --repo RooCodeInc/Roo-Code --state merged --base main --limit 1000 \
           </iteration_approach>
         </implementation>
         <message_template><![CDATA[
-Investigate PR #[number] for release notes v[version].
-1. Get PR details: gh pr view [number] --repo RooCodeInc/Roo-Code --json number,title,author,mergedAt,labels,body,url
-2. Extract linked issues from PR body
-3. Get issue details if linked
-4. Categorize change (Feature/QOL/Bug Fix/Provider Update)
-5. Identify documentation needs (new features, behavior changes, deprecations)
-6. Append to .roo/tmp/release-notes/temp_pr_analysis_v[version].md using insert_content line 0
-
-Include documentation flags:
-- docs-new: Completely new feature
-- docs-update: Existing docs need updating
-- docs-example: New examples needed
-- docs-migration: Breaking changes
-
-CRITICAL: Never create/overwrite files, only append.
-]]></message_template>
+  Investigate PR #[number] for release notes v[version].
+  1. Get PR details: gh pr view [number] --repo RooCodeInc/Roo-Code --json number,title,author,mergedAt,labels,body,url
+  2. Extract linked issues from PR body
+  3. Get issue details if linked
+  4. Categorize change (Feature/QOL/Bug Fix/Provider Update)
+  5. Identify documentation needs (new features, behavior changes, deprecations)
+  6. Append to .roo/tmp/release-notes/temp_pr_analysis_v[version].md using insert_content line 0
+  
+  Include documentation flags:
+  - docs-new: Completely new feature
+  - docs-update: Existing docs need updating
+  - docs-example: New examples needed
+  - docs-migration: Breaking changes
+  
+  CRITICAL: Never create/overwrite files, only append.
+  MANDATORY: Insert the marker line '<!-- generated-by-subtask: true -->' immediately before the '---' separator in each PR entry.
+  ]]></message_template>
         <todos_template><![CDATA[
 [ ] Fetch PR #[number] details using gh pr view --repo RooCodeInc/Roo-Code
 [ ] Extract linked issues from PR body
@@ -164,6 +166,7 @@ CRITICAL: Never create/overwrite files, only append.
 **Contributors**: [list]
 **Documentation Needs**: [none|docs-new|docs-update|docs-example|docs-migration]
 **Documentation Notes**: [If applicable, what needs documenting]
+<!-- generated-by-subtask: true -->
 
 ---
       ]]></output_format>
@@ -328,7 +331,8 @@ gh pr view N --repo RooCodeInc/Roo-Code --json number,title,author,mergedAt,labe
           <file optional="true">.roo/tmp/release-notes/temp_pr_inclusion_v[version].json</file>
         </inputs>
         <precondition>
-          If .roo/tmp/release-notes/temp_pr_inclusion_v[version].json does not exist, you MUST execute the changelog_alignment phase now to obtain an inclusion decision, then retry this step.
+          - Inclusion policy required: If .roo/tmp/release-notes/temp_pr_inclusion_v[version].json does not exist, you MUST execute the changelog_alignment phase now to obtain an inclusion decision, then retry this step.
+          - Subtask provenance required: All PR analysis entries MUST contain the marker '<!-- generated-by-subtask: true -->'. If any entries are missing this marker, HALT and re-run PR analysis via per-PR subtasks before proceeding.
         </precondition>
         <filtering>
           Include only PRs listed in "included" from .roo/tmp/release-notes/temp_pr_inclusion_v[version].json. Do not fall back to using all analyzed PRs without an explicit inclusion policy.
@@ -501,6 +505,9 @@ gh pr list --repo RooCodeInc/Roo-Code --state merged --base main --limit 1000 \
     <rule priority="CRITICAL">
       Parent task creates temp files, subtasks only append
     </rule>
+    <rule priority="CRITICAL">
+      For each PR, the parent MUST create a subtask via new_task. The parent MUST NOT write PR analysis entries; only subtasks may append to .roo/tmp/release-notes/temp_pr_analysis_v[version].md. Do not proceed to changelog_alignment or compilation until all PR subtasks complete.
+    </rule>
     <rule priority="CRITICAL">
       Use the simplified PR extraction command for consistent results
     </rule>

.roorules

@@ -11,7 +11,7 @@ This ensures links work correctly in the built documentation while maintaining c
 When making structural or formatting changes beyond simple .md or .mdx files, always check the Context7 MCP, the `context7CompatibleLibraryID` will be `/facebook/docusaurus`
 
 ## Release Notes "thank you" exclusions
-Do not thank daniel-lxs, cte, hannesrudolph, jr, roomote, app/roomote, dleffel or mrubens in release notes
+Do not thank daniel-lxs, cte, hannesrudolph, jr, roomote, app/roomote, dleffel, brunobergher or mrubens in release notes
 
 
 ## Misc

docs/features/auto-approving-actions.mdx

@@ -38,37 +38,22 @@ Auto-approve settings speed up your workflow by eliminating repetitive confirmat
 
 ## Quick Start Guide
 
-1. Click the Auto-Approve Toolbar above the chat input
-2. Select which actions Roo can perform without asking permission
-3. Use the master toggle (leftmost checkbox) to quickly enable/disable all permissions
+1. Open the Auto-Approve dropdown next to the chat input
+2. Toggle "Enabled" at the bottom-right of the dropdown to activate or pause auto-approval
+3. Use the All/None chips to bulk-select or clear permissions, or select individual tiles; you can keep Enabled On with "None" selected
+4. (Optional) Click the gear icon to open Settings for deeper per-permission controls
 
 ---
 
-## Auto-Approve Toolbar
+## Auto-Approve Dropdown
 
-<img src="/img/auto-approving-actions/auto-approving-actions.png" alt="Auto-approve toolbar collapsed state" width="600" />
+<img src="/img/auto-approving-actions/auto-approving-actions-20.png" alt="Auto-Approve dropdown with All/None chips and global Enabled toggle (bottom-right)" width="600" />
 
-*Prompt box and Auto-Approve Toolbar showing enabled permissions*
+The dropdown shows a grid of permission tiles. Controls:
+- Enabled (bottom-right): master pause/resume for auto-approval
+- All / None (bottom-left): bulk select or clear permissions without changing Enabled
+- Permission tiles: choose which actions can run without prompts; some tiles may be disabled depending on model or mode
 
-Click the toolbar to expand it and configure individual permissions:
-
-<img src="/img/auto-approving-actions/auto-approving-actions-1.png" alt="Auto-approve toolbar expanded state" width="600" />
-
-*Prompt text box and Expanded toolbar with all options*
-
-### API Request Limit
-
-The toolbar includes an input field to set the maximum number of API requests Roo can make automatically:
-
-- **Purpose**: Prevents runaway API usage and unexpected costs
-- **Default**: No limit (empty field)
-- **Recommended**: Set a reasonable limit based on your task complexity (e.g., 50-100 for most tasks)
-- **How it works**: Once the limit is exceeded, Roo will pause and show a dialog allowing you to reset the counter and continue
-
-This safety feature is particularly useful when:
-- Working with expensive API models
-- Testing new workflows
-- Letting Roo work autonomously for extended periods
 
 ### Available Permissions
 
@@ -87,30 +72,19 @@ This safety feature is particularly useful when:
 
 ---
 
-## Master Toggle for Quick Control
+## Global Enabled Switch
 
-The leftmost checkbox works as a master toggle:
+<img src="/img/auto-approving-actions/auto-approving-actions-21.png" alt="Auto-Approve dropdown; Enabled at bottom-right and All/None chips at bottom-left" width="600" />
 
-<img src="/img/auto-approving-actions/auto-approving-actions-14.png" alt="Master toggle in Auto-approve toolbar" width="600" />
+How it works:
+- Enabled On — Auto-approval runs for the permissions you’ve selected
+- Enabled Off — Pauses all auto-approvals; your per-permission selections persist
+- All / None — Bulk adjust selections while Enabled remains unchanged
 
-*Master toggle (checkbox) controls all auto-approve permissions at once*
-
-**How it works:**
-- **Checked**: Activates all configured auto-approve permissions
-- **Unchecked**: Temporarily disables all auto-approvals without changing individual settings
-- **Important**: Individual permission settings are preserved when toggling
-- **Note**: The master toggle is temporarily disabled while the auto-approve menu is expanded
-
-This means you can:
-1. Configure your preferred permissions once
-2. Use the master toggle to quickly enable/disable them all
-3. Your configuration remains intact for next time
-
-Use the master toggle when:
-- Working in sensitive code (turn off)
-- Doing rapid development (turn on)
+When to toggle:
+- Sensitive or production work → Off
+- Rapid iteration and refactors → On
 - Switching between exploration and editing tasks
-- Temporarily pausing automation without losing settings
 
 ---
 
@@ -122,11 +96,10 @@ The settings panel provides detailed control with important security context:
 
 To access these settings:
 
-1. Click <Codicon name="gear" /> in the top-right corner
+1. Click <Codicon name="gear" /> in the top-right of the dropdown
 2. Navigate to Auto-Approve Settings
 
-<img src="/img/auto-approving-actions/auto-approving-actions-19.png" alt="Settings panel auto-approve options" width="550" />
-*Complete settings panel view*
+The settings panel mirrors the same permissions with additional context and safeguards.
 
 ### Read Operations
 

docs/features/code-actions.md

@@ -62,6 +62,8 @@ The **Add to Context** action is listed first in the Code Actions menu so you ca
 
 This helps Roo understand the exact context of your code within the project, allowing it to provide more relevant and accurate assistance.
 
+Tip: Use macOS Cmd+' or Windows/Linux Ctrl+' to add the selection to context quickly. See [Keyboard Shortcuts](/features/keyboard-shortcuts).
+
 **Example Chat Input:**
 
 ```

docs/features/codebase-indexing.mdx

@@ -282,6 +282,15 @@ Use natural language descriptions:
 - Ensure the key has necessary permissions
 - For Ollama, verify the service is running
 
+### API Key Format Errors (“ByteString conversion”)
+
+- Symptom: Error mentions "ByteString conversion" during indexing or when saving settings
+- Likely cause: Your embedding provider API key contains invalid/special characters or hidden whitespace
+- Fix:
+  - Regenerate a fresh API key from your provider dashboard
+  - Paste the key again, ensuring no leading/trailing spaces or hidden characters
+  - Roo will display a clear validation message if the key is invalid
+
 ### Model Issues
 
 **"Model Not Found"**

docs/features/keyboard-shortcuts.md

@@ -3,7 +3,7 @@ description: Master keyboard navigation in Roo Code with customizable shortcuts,
 keywords:
   - keyboard shortcuts
   - keyboard navigation
-  - roo.acceptInput
+  - roo-cline.acceptInput
   - prompt history
   - accessibility
   - vim compatibility
@@ -19,12 +19,13 @@ The Roo Code interface supports keyboard navigation and shortcuts to streamline
 
 ## Available Keyboard Commands
 
-Roo Code offers keyboard commands to enhance your workflow. This page focuses on the `roo.acceptInput` command, but here's a quick reference to all keyboard commands:
+Roo Code offers keyboard commands to enhance your workflow. This page focuses on the `roo-cline.acceptInput` command, but here's a quick reference to all keyboard commands:
 
 | Command | Description | Default Shortcut |
 |---------|-------------|-----------------|
-| `roo.acceptInput` | Submit text or accept the primary suggestion | None (configurable) |
-| `roo.focus` | Focus the Roo input box | None (configurable) |
+| `roo-cline.acceptInput` | Submit text or accept the primary suggestion | None (configurable) |
+| `roo-cline.focusInput` | Focus the Roo input box | None (configurable) |
+| Add to Context | Add selected code to Roo's context | macOS: Cmd+Y; Windows/Linux: Ctrl+Y |
 | Arrow Up/Down | Navigate through prompt history | Built-in |
 
 ### Key Benefits of Keyboard Commands
@@ -36,13 +37,13 @@ Roo Code offers keyboard commands to enhance your workflow. This page focuses on
 
 ---
 
-## roo.acceptInput Command
+## roo-cline.acceptInput Command
 
-The `roo.acceptInput` command lets you submit text or accept suggestions with keyboard shortcuts instead of clicking buttons or pressing Enter in the input area.
+The `roo-cline.acceptInput` command lets you submit text or accept suggestions with keyboard shortcuts instead of clicking buttons or pressing Enter in the input area.
 
 ### What It Does
 
-The `roo.acceptInput` command is a general-purpose input submission command. When triggered, it:
+The `roo-cline.acceptInput` command is a general-purpose input submission command. When triggered, it:
 
 - Submits your current text or image input when in the text input area (equivalent to pressing Enter)
 - Clicks the primary (first) button when action buttons are visible (such as confirm/cancel buttons or any other action buttons)
@@ -53,7 +54,7 @@ The `roo.acceptInput` command is a general-purpose input submission command. Whe
 
 1. Open the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac)
 2. Type "Preferences: Open Keyboard Shortcuts"
-3. In the search box, type "roo.acceptInput"
+3. In the search box, type "roo-cline.acceptInput"
 4. Locate "Roo: Accept Input/Suggestion" in the results
 5. Click the + icon to the left of the command
 6. Press your desired key combination (e.g., `Ctrl+Enter` or `Alt+Enter`)
@@ -69,17 +70,26 @@ The `roo.acceptInput` command is a general-purpose input submission command. Whe
 ```json
 {
   "key": "ctrl+enter",  // or your preferred key combination
-  "command": "roo.acceptInput",
-  "when": "rooViewFocused"  // This is a context condition that ensures the command only works when Roo is focused
+  "command": "roo-cline.acceptInput",
+  "when": "view == roo-cline.SidebarProvider || activeWebviewPanelId == roo-cline.TabPanelProvider"
 }
 ```
 
-You can also use a more specific condition:
+Scoped examples:
+- Sidebar Roo view only:
 ```json
 {
   "key": "ctrl+enter",
-  "command": "roo.acceptInput",
-  "when": "webviewViewFocus && webviewViewId == 'roo-cline.SidebarProvider'"
+  "command": "roo-cline.acceptInput",
+  "when": "view == roo-cline.SidebarProvider"
+}
+```
+- Editor Roo tab only:
+```json
+{
+  "key": "ctrl+enter",
+  "command": "roo-cline.acceptInput",
+  "when": "activeWebviewPanelId == roo-cline.TabPanelProvider"
 }
 ```
 
@@ -92,6 +102,12 @@ Choose a key combination that doesn't conflict with existing VS Code shortcuts:
 - `Ctrl+Enter` - Intuitive for command execution
 - `Alt+A` - Mnemonic for "Accept"
 
+## Add to Context Shortcut
+
+- Default: macOS Cmd+Y; Windows/Linux Ctrl+Y
+- Requires: when condition `editorTextFocus && editorHasSelection`
+- Focus does not change automatically. To continue typing immediately, use “Roo: Focus Input” (`roo-cline.focusInput`) or click into the Roo panel.
+
 ### Practical Use Cases
 
 #### Quick Development Workflows
@@ -117,7 +133,7 @@ Choose a key combination that doesn't conflict with existing VS Code shortcuts:
 
 ### Accessibility Benefits
 
-The `roo.acceptInput` command was designed with accessibility in mind:
+The `roo-cline.acceptInput` command was designed with accessibility in mind:
 
 - **Reduced Mouse Dependence**: Complete entire workflows without reaching for the mouse
 - **Reduced Physical Strain**: Helps users who experience discomfort or pain from mouse usage
@@ -133,7 +149,7 @@ Here are some complete workflow examples showing how to effectively use keyboard
 1. Open VS Code and navigate to your project
 2. Open Roo via the sidebar
 3. Type your request: "Create a REST API endpoint for user registration"
-4. When Roo asks for framework preferences, use your `roo.acceptInput` shortcut to select the first suggestion
+4. When Roo asks for framework preferences, use your `roo-cline.acceptInput` shortcut to select the first suggestion
 5. Continue using the shortcut to accept code generation suggestions
 6. When Roo offers to save the file, use the shortcut again to confirm
 7. Use VS Code's built-in shortcuts to navigate through the created files
@@ -153,13 +169,13 @@ Here are some complete workflow examples showing how to effectively use keyboard
 | Wrong suggestion selected | The command always selects the first (primary) button; use mouse if you need a different option |
 | Conflicts with existing shortcuts | Try a different key combination in VS Code keyboard settings |
 | No visual feedback when used | This is normal - the command silently activates the function without visual confirmation |
-| Shortcut works inconsistently | Make sure the `when` clause is properly configured in your keybindings.json (either `rooViewFocused` or the webview-specific condition) |
+| Shortcut works inconsistently | Make sure the `when` clause is properly configured (use `view == roo-cline.SidebarProvider` or `activeWebviewPanelId == roo-cline.TabPanelProvider`) |
 
 ### Technical Implementation
 
-The `roo.acceptInput` command is implemented as follows:
+The `roo-cline.acceptInput` command is implemented as follows:
 
-- Command registered as `roo.acceptInput` with display title "Roo: Accept Input/Suggestion" in the command palette
+- Command registered as `roo-cline.acceptInput` with display title "Roo: Accept Input/Suggestion" in the command palette
 - When triggered, it sends an "acceptInput" message to the active Roo webview
 - The webview determines the appropriate action based on the current UI state:
   - Clicks the primary action button if action buttons are visible and enabled