Major Enhancements:

- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
  - Default installation location changed to .bmad (hidden directory) for cleaner project root organization

    Web Bundle Improvements:

    - All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
    - Advanced elicitation capabilities integrated into standalone agents
    - All bundles enhanced with party mode agent manifests
    - Added default-party.csv files to bmm, bmgd, and cis module teams
    - The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
    - New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)

    Phase 4 Workflow Updates (In Progress):

    - Initiated shift to separate phase 4 implementation artifacts from documentation
        - Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
        - Installer questions and configuration added for artifact path selection
        - Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates

    Additional Changes:

    - New agent and action command header models for standardization
    - Enhanced web-bundle-activation-steps fragment
    - Updated web-bundler.js to support new structure
    - VS Code settings updated for new .bmad directory
    - Party mode instructions and workflow enhanced for better orchestration

   IDE Installer Updates:

    - Show version number of installer in cli
    - improved Installer UX
    - Gemini TOML Improved to have clear loading instructions with @ commands
    - All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.

tools/cli/installers/lib/ide/trae.js

@@ -40,7 +40,7 @@ class TraeSetup extends BaseIdeSetup {
     let agentCount = 0;
     for (const agent of agents) {
       const content = await this.readFile(agent.path);
-      const processedContent = this.createAgentRule(agent, content, bmadDir, projectDir);
+      const processedContent = await this.createAgentRule(agent, content, bmadDir, projectDir);
 
       // Use bmad- prefix: bmad-agent-{module}-{name}.md
       const targetPath = path.join(rulesDir, `bmad-agent-${agent.module}-${agent.name}.md`);
@@ -108,7 +108,7 @@ class TraeSetup extends BaseIdeSetup {
   /**
    * Create rule content for an agent
    */
-  createAgentRule(agent, content, bmadDir, projectDir) {
+  async createAgentRule(agent, content, bmadDir, projectDir) {
     // Extract metadata from agent content
     const titleMatch = content.match(/title="([^"]+)"/);
     const title = titleMatch ? titleMatch[1] : this.formatTitle(agent.name);
@@ -116,6 +116,9 @@ class TraeSetup extends BaseIdeSetup {
     const iconMatch = content.match(/icon="([^"]+)"/);
     const icon = iconMatch ? iconMatch[1] : '🤖';
 
+    // Get the activation header from central template
+    const activationHeader = await this.getAgentCommandHeader();
+
     // Extract YAML content if available
     const yamlMatch = content.match(/```ya?ml\r?\n([\s\S]*?)```/);
     const yamlContent = yamlMatch ? yamlMatch[1] : content;
@@ -129,7 +132,9 @@ This rule is triggered when the user types \`@${agent.name}\` and activates the
 
 ## Agent Activation
 
-CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+${activationHeader}
+
+Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 \`\`\`yaml
 ${yamlContent}
@@ -143,9 +148,6 @@ The complete agent definition is available in [${relativePath}](${relativePath})
 
 When the user types \`@${agent.name}\`, activate this ${title} persona and follow all instructions defined in the YAML configuration above.
 
-## Module
-
-Part of the BMAD ${agent.module.toUpperCase()} module.
 `;
 
     return ruleContent;