style: standardize quotes and formatting across YAML and JS files

.github/workflows/promote-to-stable.yml

@@ -4,9 +4,9 @@ on:
   workflow_dispatch:
     inputs:
       version_bump:
-        description: 'Version bump type'
+        description: "Version bump type"
         required: true
-        default: 'minor'
+        default: "minor"
         type: choice
         options:
           - patch
@@ -30,8 +30,8 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version: "20"
-          registry-url: 'https://registry.npmjs.org'
+          registry-url: "https://registry.npmjs.org"
 
       - name: Configure Git
         run: |

bmad-core/data/test-levels-framework.md

@@ -25,10 +25,10 @@ Comprehensive guide for determining appropriate test levels (unit, integration,
 
 ```yaml
 unit_test:
-  component: "PriceCalculator"
+  component: 'PriceCalculator'
-  scenario: "Calculate discount with multiple rules"
+  scenario: 'Calculate discount with multiple rules'
-  justification: "Complex business logic with multiple branches"
+  justification: 'Complex business logic with multiple branches'
-  mock_requirements: "None - pure function"
+  mock_requirements: 'None - pure function'
 ```
 
 ### Integration Tests
@@ -52,10 +52,10 @@ unit_test:
 
 ```yaml
 integration_test:
-  components: ["UserService", "AuthRepository"]
+  components: ['UserService', 'AuthRepository']
-  scenario: "Create user with role assignment"
+  scenario: 'Create user with role assignment'
-  justification: "Critical data flow between service and persistence"
+  justification: 'Critical data flow between service and persistence'
-  test_environment: "In-memory database"
+  test_environment: 'In-memory database'
 ```
 
 ### End-to-End Tests
@@ -79,10 +79,10 @@ integration_test:
 
 ```yaml
 e2e_test:
-  journey: "Complete checkout process"
+  journey: 'Complete checkout process'
-  scenario: "User purchases with saved payment method"
+  scenario: 'User purchases with saved payment method'
-  justification: "Revenue-critical path requiring full validation"
+  justification: 'Revenue-critical path requiring full validation'
-  environment: "Staging with test payment gateway"
+  environment: 'Staging with test payment gateway'
 ```
 
 ## Test Level Selection Rules

bmad-core/tasks/nfr-assess.md

@@ -6,18 +6,19 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
 
 ```yaml
 required:
-  - story_id: "{epic}.{story}"  # e.g., "1.3"
+  - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: "docs/stories/{epic}.{story}.*.md"
+  - story_path: 'docs/stories/{epic}.{story}.*.md'
 
 optional:
-  - architecture_refs: "docs/architecture/*.md"
+  - architecture_refs: 'docs/architecture/*.md'
-  - technical_preferences: "docs/technical-preferences.md"
+  - technical_preferences: 'docs/technical-preferences.md'
   - acceptance_criteria: From story file
 ```
 
 ## Purpose
 
 Assess non-functional requirements for a story and generate:
+
 1. YAML block for the gate file's `nfr_validation` section
 2. Brief markdown assessment saved to `docs/qa/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md`
 
@@ -26,6 +27,7 @@ Assess non-functional requirements for a story and generate:
 ### 0. Fail-safe for Missing Inputs
 
 If story_path or story file can't be found:
+
 - Still create assessment file with note: "Source story not found"
 - Set all selected NFRs to CONCERNS with notes: "Target unknown / evidence missing"
 - Continue with assessment to provide value
@@ -52,6 +54,7 @@ Which NFRs should I assess? (Enter numbers or press Enter for default)
 ### 2. Check for Thresholds
 
 Look for NFR requirements in:
+
 - Story acceptance criteria
 - `docs/architecture/*.md` files
 - `docs/technical-preferences.md`
@@ -72,6 +75,7 @@ No security requirements found. Required auth method?
 ### 3. Quick Assessment
 
 For each selected NFR, check:
+
 - Is there evidence it's implemented?
 - Can we validate it?
 - Are there obvious gaps?
@@ -88,16 +92,16 @@ nfr_validation:
   _assessed: [security, performance, reliability, maintainability]
   security:
     status: CONCERNS
-    notes: "No rate limiting on auth endpoints"
+    notes: 'No rate limiting on auth endpoints'
   performance:
     status: PASS
-    notes: "Response times < 200ms verified"
+    notes: 'Response times < 200ms verified'
   reliability:
     status: PASS
-    notes: "Error handling and retries implemented"
+    notes: 'Error handling and retries implemented'
   maintainability:
     status: CONCERNS
-    notes: "Test coverage at 65%, target is 80%"
+    notes: 'Test coverage at 65%, target is 80%'
 ```
 
 ## Deterministic Status Rules
@@ -123,18 +127,21 @@ If `technical-preferences.md` defines custom weights, use those instead.
 
 ```markdown
 # NFR Assessment: {epic}.{story}
+
 Date: {date}
 Reviewer: Quinn
 
 <!-- Note: Source story not found (if applicable) -->
 
 ## Summary
+
 - Security: CONCERNS - Missing rate limiting
 - Performance: PASS - Meets <200ms requirement
 - Reliability: PASS - Proper error handling
 - Maintainability: CONCERNS - Test coverage below target
 
 ## Critical Issues
+
 1. **No rate limiting** (Security)
    - Risk: Brute force attacks possible
    - Fix: Add rate limiting middleware to auth endpoints
@@ -144,6 +151,7 @@ Reviewer: Quinn
    - Fix: Add tests for uncovered branches
 
 ## Quick Wins
+
 - Add rate limiting: ~2 hours
 - Increase test coverage: ~4 hours
 - Add performance monitoring: ~1 hour
@@ -152,6 +160,7 @@ Reviewer: Quinn
 ## Output 3: Story Update Line
 
 **End with this line for the review task to quote:**
+
 ```
 NFR assessment: docs/qa/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
 ```
@@ -159,6 +168,7 @@ NFR assessment: docs/qa/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
 ## Output 4: Gate Integration Line
 
 **Always print at the end:**
+
 ```
 Gate NFR block ready → paste into docs/qa/gates/{epic}.{story}-{slug}.yml under nfr_validation
 ```
@@ -166,66 +176,82 @@ Gate NFR block ready → paste into docs/qa/gates/{epic}.{story}-{slug}.yml unde
 ## Assessment Criteria
 
 ### Security
+
 **PASS if:**
+
 - Authentication implemented
 - Authorization enforced
 - Input validation present
 - No hardcoded secrets
 
 **CONCERNS if:**
+
 - Missing rate limiting
 - Weak encryption
 - Incomplete authorization
 
 **FAIL if:**
+
 - No authentication
 - Hardcoded credentials
 - SQL injection vulnerabilities
 
 ### Performance
+
 **PASS if:**
+
 - Meets response time targets
 - No obvious bottlenecks
 - Reasonable resource usage
 
 **CONCERNS if:**
+
 - Close to limits
 - Missing indexes
 - No caching strategy
 
 **FAIL if:**
+
 - Exceeds response time limits
 - Memory leaks
 - Unoptimized queries
 
 ### Reliability
+
 **PASS if:**
+
 - Error handling present
 - Graceful degradation
 - Retry logic where needed
 
 **CONCERNS if:**
+
 - Some error cases unhandled
 - No circuit breakers
 - Missing health checks
 
 **FAIL if:**
+
 - No error handling
 - Crashes on errors
 - No recovery mechanisms
 
 ### Maintainability
+
 **PASS if:**
+
 - Test coverage meets target
 - Code well-structured
 - Documentation present
 
 **CONCERNS if:**
+
 - Test coverage below target
 - Some code duplication
 - Missing documentation
 
 **FAIL if:**
+
 - No tests
 - Highly coupled code
 - No documentation
@@ -291,6 +317,7 @@ maintainability:
 8. **Portability**: Adaptability, installability
 
 Use these when assessing beyond the core four.
+
 </details>
 
 <details>
@@ -304,12 +331,13 @@ performance_deep_dive:
     p99: 350ms
   database:
     slow_queries: 2
-    missing_indexes: ["users.email", "orders.user_id"]
+    missing_indexes: ['users.email', 'orders.user_id']
   caching:
     hit_rate: 0%
-    recommendation: "Add Redis for session data"
+    recommendation: 'Add Redis for session data'
   load_test:
     max_rps: 150
     breaking_point: 200 rps
 ```
+
 </details>

bmad-core/tasks/qa-gate.md

@@ -27,11 +27,11 @@ Slug rules:
 
 ```yaml
 schema: 1
-story: "{epic}.{story}"
+story: '{epic}.{story}'
 gate: PASS|CONCERNS|FAIL|WAIVED
-status_reason: "1-2 sentence explanation of gate decision"
+status_reason: '1-2 sentence explanation of gate decision'
-reviewer: "Quinn"
+reviewer: 'Quinn'
-updated: "{ISO-8601 timestamp}"
+updated: '{ISO-8601 timestamp}'
 top_issues: [] # Empty array if no issues
 waiver: { active: false } # Only set active: true if WAIVED
 ```
@@ -40,20 +40,20 @@ waiver: { active: false } # Only set active: true if WAIVED
 
 ```yaml
 schema: 1
-story: "1.3"
+story: '1.3'
 gate: CONCERNS
-status_reason: "Missing rate limiting on auth endpoints poses security risk."
+status_reason: 'Missing rate limiting on auth endpoints poses security risk.'
-reviewer: "Quinn"
+reviewer: 'Quinn'
-updated: "2025-01-12T10:15:00Z"
+updated: '2025-01-12T10:15:00Z'
 top_issues:
-  - id: "SEC-001"
+  - id: 'SEC-001'
     severity: high # ONLY: low|medium|high
-    finding: "No rate limiting on login endpoint"
+    finding: 'No rate limiting on login endpoint'
-    suggested_action: "Add rate limiting middleware before production"
+    suggested_action: 'Add rate limiting middleware before production'
-  - id: "TEST-001"
+  - id: 'TEST-001'
     severity: medium
-    finding: "No integration tests for auth flow"
+    finding: 'No integration tests for auth flow'
-    suggested_action: "Add integration test coverage"
+    suggested_action: 'Add integration test coverage'
 waiver: { active: false }
 ```
 
@@ -61,20 +61,20 @@ waiver: { active: false }
 
 ```yaml
 schema: 1
-story: "1.3"
+story: '1.3'
 gate: WAIVED
-status_reason: "Known issues accepted for MVP release."
+status_reason: 'Known issues accepted for MVP release.'
-reviewer: "Quinn"
+reviewer: 'Quinn'
-updated: "2025-01-12T10:15:00Z"
+updated: '2025-01-12T10:15:00Z'
 top_issues:
-  - id: "PERF-001"
+  - id: 'PERF-001'
     severity: low
-    finding: "Dashboard loads slowly with 1000+ items"
+    finding: 'Dashboard loads slowly with 1000+ items'
-    suggested_action: "Implement pagination in next sprint"
+    suggested_action: 'Implement pagination in next sprint'
 waiver:
   active: true
-  reason: "MVP release - performance optimization deferred"
+  reason: 'MVP release - performance optimization deferred'
-  approved_by: "Product Owner"
+  approved_by: 'Product Owner'
 ```
 
 ## Gate Decision Criteria

bmad-core/tasks/risk-profile.md

@@ -6,10 +6,10 @@ Generate a comprehensive risk assessment matrix for a story implementation using
 
 ```yaml
 required:
-  - story_id: "{epic}.{story}" # e.g., "1.3"
+  - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: "docs/stories/{epic}.{story}.*.md"
+  - story_path: 'docs/stories/{epic}.{story}.*.md'
-  - story_title: "{title}" # If missing, derive from story file H1
+  - story_title: '{title}' # If missing, derive from story file H1
-  - story_slug: "{slug}" # If missing, derive from title (lowercase, hyphenated)
+  - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
 ```
 
 ## Purpose
@@ -79,14 +79,14 @@ For each category, identify specific risks:
 
 ```yaml
 risk:
-  id: "SEC-001" # Use prefixes: SEC, PERF, DATA, BUS, OPS, TECH
+  id: 'SEC-001' # Use prefixes: SEC, PERF, DATA, BUS, OPS, TECH
   category: security
-  title: "Insufficient input validation on user forms"
+  title: 'Insufficient input validation on user forms'
-  description: "Form inputs not properly sanitized could lead to XSS attacks"
+  description: 'Form inputs not properly sanitized could lead to XSS attacks'
   affected_components:
-    - "UserRegistrationForm"
+    - 'UserRegistrationForm'
-    - "ProfileUpdateForm"
+    - 'ProfileUpdateForm'
-  detection_method: "Code review revealed missing validation"
+  detection_method: 'Code review revealed missing validation'
 ```
 
 ### 2. Risk Assessment
@@ -133,20 +133,20 @@ For each identified risk, provide mitigation:
 
 ```yaml
 mitigation:
-  risk_id: "SEC-001"
+  risk_id: 'SEC-001'
-  strategy: "preventive" # preventive|detective|corrective
+  strategy: 'preventive' # preventive|detective|corrective
   actions:
-    - "Implement input validation library (e.g., validator.js)"
+    - 'Implement input validation library (e.g., validator.js)'
-    - "Add CSP headers to prevent XSS execution"
+    - 'Add CSP headers to prevent XSS execution'
-    - "Sanitize all user inputs before storage"
+    - 'Sanitize all user inputs before storage'
-    - "Escape all outputs in templates"
+    - 'Escape all outputs in templates'
   testing_requirements:
-    - "Security testing with OWASP ZAP"
+    - 'Security testing with OWASP ZAP'
-    - "Manual penetration testing of forms"
+    - 'Manual penetration testing of forms'
-    - "Unit tests for validation functions"
+    - 'Unit tests for validation functions'
-  residual_risk: "Low - Some zero-day vulnerabilities may remain"
+  residual_risk: 'Low - Some zero-day vulnerabilities may remain'
-  owner: "dev"
+  owner: 'dev'
-  timeline: "Before deployment"
+  timeline: 'Before deployment'
 ```
 
 ## Outputs
@@ -172,12 +172,12 @@ risk_summary:
   highest:
     id: SEC-001
     score: 9
-    title: "XSS on profile form"
+    title: 'XSS on profile form'
   recommendations:
     must_fix:
-      - "Add input sanitization & CSP"
+      - 'Add input sanitization & CSP'
     monitor:
-      - "Add security alerts for auth endpoints"
+      - 'Add security alerts for auth endpoints'
 ```
 
 ### Output 2: Markdown Report

bmad-core/tasks/test-design.md

@@ -6,10 +6,10 @@ Create comprehensive test scenarios with appropriate test level recommendations
 
 ```yaml
 required:
-  - story_id: "{epic}.{story}" # e.g., "1.3"
+  - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: "{devStoryLocation}/{epic}.{story}.*.md" # Path from core-config.yaml
+  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
-  - story_title: "{title}" # If missing, derive from story file H1
+  - story_title: '{title}' # If missing, derive from story file H1
-  - story_slug: "{slug}" # If missing, derive from title (lowercase, hyphenated)
+  - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
 ```
 
 ## Purpose
@@ -62,13 +62,13 @@ For each identified test need, create:
 
 ```yaml
 test_scenario:
-  id: "{epic}.{story}-{LEVEL}-{SEQ}"
+  id: '{epic}.{story}-{LEVEL}-{SEQ}'
-  requirement: "AC reference"
+  requirement: 'AC reference'
   priority: P0|P1|P2|P3
   level: unit|integration|e2e
-  description: "What is being tested"
+  description: 'What is being tested'
-  justification: "Why this level was chosen"
+  justification: 'Why this level was chosen'
-  mitigates_risks: ["RISK-001"] # If risk profile exists
+  mitigates_risks: ['RISK-001'] # If risk profile exists
 ```
 
 ### 5. Validate Coverage

bmad-core/tasks/trace-requirements.md

@@ -31,21 +31,21 @@ Identify all testable requirements from:
 For each requirement, document which tests validate it. Use Given-When-Then to describe what the test validates (not how it's written):
 
 ```yaml
-requirement: "AC1: User can login with valid credentials"
+requirement: 'AC1: User can login with valid credentials'
 test_mappings:
-  - test_file: "auth/login.test.ts"
+  - test_file: 'auth/login.test.ts'
-    test_case: "should successfully login with valid email and password"
+    test_case: 'should successfully login with valid email and password'
     # Given-When-Then describes WHAT the test validates, not HOW it's coded
-    given: "A registered user with valid credentials"
+    given: 'A registered user with valid credentials'
-    when: "They submit the login form"
+    when: 'They submit the login form'
-    then: "They are redirected to dashboard and session is created"
+    then: 'They are redirected to dashboard and session is created'
     coverage: full
 
-  - test_file: "e2e/auth-flow.test.ts"
+  - test_file: 'e2e/auth-flow.test.ts'
-    test_case: "complete login flow"
+    test_case: 'complete login flow'
-    given: "User on login page"
+    given: 'User on login page'
-    when: "Entering valid credentials and submitting"
+    when: 'Entering valid credentials and submitting'
-    then: "Dashboard loads with user data"
+    then: 'Dashboard loads with user data'
     coverage: integration
 ```
 
@@ -67,19 +67,19 @@ Document any gaps found:
 
 ```yaml
 coverage_gaps:
-  - requirement: "AC3: Password reset email sent within 60 seconds"
+  - requirement: 'AC3: Password reset email sent within 60 seconds'
-    gap: "No test for email delivery timing"
+    gap: 'No test for email delivery timing'
     severity: medium
     suggested_test:
       type: integration
-      description: "Test email service SLA compliance"
+      description: 'Test email service SLA compliance'
 
-  - requirement: "AC5: Support 1000 concurrent users"
+  - requirement: 'AC5: Support 1000 concurrent users'
-    gap: "No load testing implemented"
+    gap: 'No load testing implemented'
     severity: high
     suggested_test:
       type: performance
-      description: "Load test with 1000 concurrent connections"
+      description: 'Load test with 1000 concurrent connections'
 ```
 
 ## Outputs
@@ -95,11 +95,11 @@ trace:
     full: Y
     partial: Z
     none: W
-  planning_ref: "docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md"
+  planning_ref: 'docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md'
   uncovered:
-    - ac: "AC3"
+    - ac: 'AC3'
-      reason: "No test found for password reset timing"
+      reason: 'No test found for password reset timing'
-  notes: "See docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md"
+  notes: 'See docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md'
 ```
 
 ### Output 2: Traceability Report

docs/enhanced-ide-development-workflow.md

@@ -30,7 +30,7 @@ The Test Architect (Quinn) provides comprehensive quality assurance throughout t
 ### Quick Command Reference
 
 | **Stage**                | **Command** | **Purpose**                             | **Output**                                                      | **Priority**                |
-|-----------|------------|-------------|------------|--------------|
+| ------------------------ | ----------- | --------------------------------------- | --------------------------------------------------------------- | --------------------------- |
 | **After Story Approval** | `*risk`     | Identify integration & regression risks | `docs/qa/assessments/{epic}.{story}-risk-{YYYYMMDD}.md`         | High for complex/brownfield |
 |                          | `*design`   | Create test strategy for dev            | `docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md`  | High for new features       |
 | **During Development**   | `*trace`    | Verify test coverage                    | `docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md`        | Medium                      |
@@ -135,7 +135,7 @@ The Test Architect (Quinn) provides comprehensive quality assurance throughout t
 ### Understanding Gate Decisions
 
 | **Status**   | **Meaning**                                  | **Action Required**     | **Can Proceed?** |
-|------------|-------------|-------------------|------------------|
+| ------------ | -------------------------------------------- | ----------------------- | ---------------- |
 | **PASS**     | All critical requirements met                | None                    | ✅ Yes           |
 | **CONCERNS** | Non-critical issues found                    | Team review recommended | ⚠️ With caution  |
 | **FAIL**     | Critical issues (security, missing P0 tests) | Must fix                | ❌ No            |
@@ -146,7 +146,7 @@ The Test Architect (Quinn) provides comprehensive quality assurance throughout t
 The Test Architect uses risk scoring to prioritize testing:
 
 | **Risk Score** | **Calculation**                | **Testing Priority**      | **Gate Impact**          |
-|---------------|----------------|-------------------|----------------|
+| -------------- | ------------------------------ | ------------------------- | ------------------------ |
 | **9**          | High probability × High impact | P0 - Must test thoroughly | FAIL if untested         |
 | **6**          | Medium-high combinations       | P1 - Should test well     | CONCERNS if gaps         |
 | **4**          | Medium combinations            | P1 - Should test          | CONCERNS if notable gaps |
@@ -228,7 +228,7 @@ All Test Architect activities create permanent records:
 **Should I run Test Architect commands?**
 
 | **Scenario**             | **Before Dev**                  | **During Dev**               | **After Dev**                |
-|-------------|---------------|----------------|---------------|
+| ------------------------ | ------------------------------- | ---------------------------- | ---------------------------- |
 | **Simple bug fix**       | Optional                        | Optional                     | Required `*review`           |
 | **New feature**          | Recommended `*risk`, `*design`  | Optional `*trace`            | Required `*review`           |
 | **Brownfield change**    | **Required** `*risk`, `*design` | Recommended `*trace`, `*nfr` | Required `*review`           |

docs/user-guide.md

@@ -377,7 +377,7 @@ Manages quality gate decisions:
 The Test Architect provides value throughout the entire development lifecycle. Here's when and how to leverage each capability:
 
 | **Stage**          | **Command** | **When to Use**         | **Value**                  | **Output**                                                     |
-|-----------|------------|-----------------|-----------|------------|
+| ------------------ | ----------- | ----------------------- | -------------------------- | -------------------------------------------------------------- |
 | **Story Drafting** | `*risk`     | After SM drafts story   | Identify pitfalls early    | `docs/qa/assessments/{epic}.{story}-risk-{YYYYMMDD}.md`        |
 |                    | `*design`   | After risk assessment   | Guide dev on test strategy | `docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md` |
 | **Development**    | `*trace`    | Mid-implementation      | Verify test coverage       | `docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md`       |

tools/installer/bin/bmad.js

@@ -7,7 +7,7 @@ const yaml = require('js-yaml');
 const chalk = require('chalk').default || require('chalk');
 const inquirer = require('inquirer').default || require('inquirer');
 const semver = require('semver');
-const https = require('https');
+const https = require('node:https');
 
 // Handle both execution contexts (from root via npx or from installer directory)
 let version;
@@ -106,7 +106,7 @@ program
     console.log('Checking for updates...');
 
     // Make HTTP request to npm registry for latest version info
-    const req = https.get(`https://registry.npmjs.org/${packageName}/latest`, res => {
+    const req = https.get(`https://registry.npmjs.org/${packageName}/latest`, (res) => {
       // Check for HTTP errors (non-200 status codes)
       if (res.statusCode !== 200) {
         console.error(chalk.red(`Update check failed: Received status code ${res.statusCode}`));
@@ -115,7 +115,7 @@ program
 
       // Accumulate response data chunks
       let data = '';
-      res.on('data', chunk => data += chunk);
+      res.on('data', (chunk) => (data += chunk));
 
       // Process complete response
       res.on('end', () => {
@@ -125,7 +125,9 @@ program
 
           // Compare versions using semver
           if (semver.gt(latest, version)) {
-            console.log(chalk.bold.blue(`⚠️  ${packageName} update available: ${version} → ${latest}`));
+            console.log(
+              chalk.bold.blue(`⚠️  ${packageName} update available: ${version} → ${latest}`),
+            );
             console.log(chalk.bold.blue('\nInstall latest by running:'));
             console.log(chalk.bold.magenta(`  npm install ${packageName}@latest`));
             console.log(chalk.dim('  or'));
@@ -141,12 +143,12 @@ program
     });
 
     // Handle network/connection errors
-    req.on('error', error => {
+    req.on('error', (error) => {
       console.error(chalk.red('Update check failed:'), error.message);
     });
 
     // Set 30 second timeout to prevent hanging
-    req.setTimeout(30000, () => {
+    req.setTimeout(30_000, () => {
       req.destroy();
       console.error(chalk.red('Update check timed out'));
     });

tools/installer/lib/ide-base-setup.js

@@ -3,7 +3,7 @@
  * Reduces duplication and provides shared methods
  */
 
-const path = require('path');
+const path = require('node:path');
 const fs = require('fs-extra');
 const yaml = require('js-yaml');
 const chalk = require('chalk').default || require('chalk');