docs: update README links to renamed orchestrator config files

## CHANGES

- Update orchestrator link to ide-bmad-orchestrator.md
- Update config link to ide-bmad-orchestrator.cfg.md
- Fix Markdownlint errors in ide-bmad-orchestrator.cfg.md

README.md

@@ -18,7 +18,7 @@ Here are the more [Setup and Usage Instructions](./docs/instruction.md) for IDE,
 
 Starting with the latest version of the BMad Agents for the BMad Method is very easy - all you need to do is copy `bmad-agent` folder to your project. The dedicated dev and sm that existing in previous versions are still available and are in the `bmad-agent/personas` folder with the .ide.md extension. Copy and paste the contents into your specific IDE's method of configuring a custom agent mode. The dev and sm both are configured for architecture and prd artifacts to be in (project-root)/docs and stories will be generated and developed in/from your (project-root)/docs/stories.
 
-For all other agent use (including the dev and sm) you can set up the [ide orchestrator](bmad-agent/bmad-agent.ide.md) - you can ask the orchestrator bmad to become any agent you have [configured](bmad-agent/bmad-orchestrator.ide.cfg.md).
+For all other agent use (including the dev and sm) you can set up the [ide orchestrator](bmad-agent/ide-bmad-orchestrator.md) - you can ask the orchestrator bmad to become any agent you have [configured](bmad-agent/ide-bmad-orchestrator.cfg.md).
 
 [General IDE Custom Mode Setup](./docs/ide-setup.md).
 

bmad-agent/ide-bmad-orchestrator.md

@@ -12,7 +12,7 @@
 
 ## Critical Start-Up & Operational Workflow
 
-### 1. Initialization & User Interaction Prompt:
+### 1. Initialization & User Interaction Prompt
 
 - CRITICAL: Your FIRST action: Load & parse `configFile` (hereafter "Config"). This Config defines ALL available personas, their associated tasks, and resource paths. If Config is missing or unparsable, inform user that you cannot locate the config and can only operate as a BMad Method Advisor (based on the kb data).
   Greet the user concisely (e.g., "BMad IDE Orchestrator ready. Config loaded. Select Agent, or I can remain in Advisor mode.").
@@ -20,7 +20,7 @@
   - Based on the loaded Config, list available specialist personas by their `Title` (and `Name` if distinct) along with their `Description`. For each persona, list the display names of its configured `Tasks`.
   - Ask: "Which persona shall I become, and what task should it perform?" Await user's specific choice.
 
-### 2. Persona Activation & Task Execution:
+### 2. Persona Activation & Task Execution
 
 - **A. Activate Persona:**
   - From the user's request, identify the target persona by matching against `Title` or `Name` in the Config.
@@ -39,7 +39,7 @@
     - **If an "In Memory" task:** Follow as stated internally.
   - Upon task completion continue interacting as the active persona.
 
-### 3. Handling Requests for Persona Change (While a Persona is Active):
+### 3. Handling Requests for Persona Change (While a Persona is Active)
 
 - If you are currently embodying a specialist persona and the user requests to become a _different_ persona, suggest starting new chat, but let them choose to `Proceed (y/n)?`
 - **If user chooses to override:**