fix: corrected cursor agent update instructions

dist/agents/bmad-orchestrator.txt

@@ -295,7 +295,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 - If `workflow.trackProgress: true`, check for active plan using utils#plan-management
 - If plan exists and this document creation is part of the plan:
   - Verify this is the expected next step
-  - If out of sequence and `enforceSequence: true`, warn user
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
   - If out of sequence and `enforceSequence: false`, ask for confirmation
 - Continue with normal execution after plan check
 
@@ -303,7 +303,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 
 - Load from `templates#*` or `{root}/templates directory`
 - Agent-specific templates are listed in agent's dependencies
-- If agent has `templates: [prd-tmpl, architecture-tmpl]`, offer to create "PRD" and "Architecture" documents
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
 ### 2. Ask Interaction Mode
 
@@ -745,6 +745,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
 [[LLM: First load core-config.yml to get plan settings]]
 
 Check workflow configuration:
+
 - `workflow.planFile` - Location of the plan (default: docs/workflow-plan.md)
 - `workflow.trackProgress` - Whether tracking is enabled
 - `workflow.updateOnCompletion` - Whether to auto-update on task completion
@@ -756,6 +757,7 @@ If tracking is disabled, inform user and exit.
 [[LLM: Check if workflow plan exists at configured location]]
 
 If no plan exists:
+
 ```
 No active workflow plan found at {location}.
 Would you like to create one? Use *plan command.
@@ -785,6 +787,7 @@ Please select an option (1-6):
 [[LLM: Read and parse the plan to understand current state]]
 
 Extract:
+
 - All steps with their checkbox status
 - Step IDs from comments (if present)
 - Current completion percentage
@@ -851,6 +854,7 @@ If user selected option 5:
 [[LLM: When called automatically by another task]]
 
 If called with parameters:
+
 ```
 task: {task_name}
 step_id: {step_identifier}
@@ -859,6 +863,7 @@ note: {optional_note}
 ```
 
 Automatically:
+
 1. Find the corresponding step
 2. Update its status
 3. Add completion metadata
@@ -891,6 +896,7 @@ Plan location: {file_path}
 Other tasks can integrate by:
 
 1. **After Task Completion**:
+
 ```
 At end of task execution:
 - Check if task corresponds to a plan step
@@ -901,6 +907,7 @@ At end of task execution:
 ```
 
 2. **On Task Failure**:
+
 ```
 If task fails:
 - Call update-workflow-plan with:
@@ -1071,6 +1078,7 @@ npx bmad-method install
   - **Windsurf**: Built-in AI capabilities
   - **Cline**: VS Code extension with AI features
   - **Roo Code**: Web-based IDE with agent support
+  - **VS Code Copilot**: AI-powered coding assistant
 
 **Note for VS Code Users**: BMAD-METHOD assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMAD agents. The installer includes built-in support for Cline and Roo.
 
@@ -1256,6 +1264,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 - **Cursor**: `@agent-name` (e.g., `@bmad-master`)
 - **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
 - **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+- **VS Code Copilot**: Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
 
 **Chat Management Guidelines**:
 - **Claude Code, Cursor, Windsurf**: Start new chats when switching agents