specweave 0.33.5 → 0.34.0

package/plugins/specweave/commands/{specweave-update-scope.md → update-scope.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:update-scope
+name: sw:update-scope
 description: Update living completion report with scope changes during increment execution
 ---
 
@@ -50,13 +50,13 @@ Future: "Why was Task 5 removed?" → Check report, find exact reason
 ### Quick Log
 
 ```bash
-/specweave:update-scope "Added dark mode toggle (stakeholder request from CMO, +16 hours)"
+/sw:update-scope "Added dark mode toggle (stakeholder request from CMO, +16 hours)"
 ```
 
 ### Detailed Log
 
 ```bash
-/specweave:update-scope
+/sw:update-scope
 # Interactive prompts:
 # - What changed? (Added/Removed/Modified user story)
 # - What specifically? (e.g., "US6: Dark mode toggle")
@@ -80,7 +80,7 @@ const active = await MetadataManager.getActive();
 
 if (active.length === 0) {
   console.error('❌ No active increment found');
-  console.error('   Run /specweave:status to check increment status');
+  console.error('   Run /sw:status to check increment status');
   process.exit(1);
 }
 
@@ -107,7 +107,7 @@ const reportPath = `.specweave/increments/${increment}/reports/COMPLETION-REPORT
 if (!fs.existsSync(reportPath)) {
   console.error('❌ Completion report not found');
   console.error(`   Expected: ${reportPath}`);
-  console.error('   Run /specweave:increment to create increment properly');
+  console.error('   Run /sw:increment to create increment properly');
   process.exit(1);
 }
 
@@ -342,9 +342,9 @@ Always include:
 
 ## Related Commands
 
-- `/specweave:increment "feature"` - Creates increment with initial completion report
-- `/specweave:done <id>` - Finalizes report and marks increment complete
-- `/specweave:status` - Check which increment is active
+- `/sw:increment "feature"` - Creates increment with initial completion report
+- `/sw:done <id>` - Finalizes report and marks increment complete
+- `/sw:status` - Check which increment is active
 
 ---
 

package/plugins/specweave/commands/{specweave-update-status.md → update-status.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:update-status
+name: sw:update-status
 description: Force-update status line cache with latest increment status
 ---
 
@@ -11,7 +11,7 @@ description: Force-update status line cache with latest increment status
 - Status line doesn't reflect recent changes
 - After completing tasks (want to see updated progress immediately)
 - After status transitions (active → completed)
-- Before checking progress with `/specweave:progress`
+- Before checking progress with `/sw:progress`
 - When status line shows outdated information
 
 ---
@@ -44,7 +44,7 @@ description: Force-update status line cache with latest increment status
 
 ```bash
 # Force-update status line (no arguments)
-/specweave:update-status
+/sw:update-status
 ```
 
 **Output**:
@@ -72,15 +72,15 @@ Status Line: [0043] ████████ 8/8 tasks (1 open) ✓
 
 This command is automatically called by:
 
-1. **`/specweave:progress`**
+1. **`/sw:progress`**
    - Ensures status line is fresh before showing progress
    - User always sees accurate completion percentages
 
-2. **`/specweave:done`**
+2. **`/sw:done`**
    - Refreshes status line before PM validation
    - Ensures final progress is accurate
 
-3. **`/specweave:status`**
+3. **`/sw:status`**
    - Updates cache before showing increment list
    - Shows current increment status
 

package/plugins/specweave/commands/{specweave-validate-features.md → validate-features.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:validate-features
+name: sw:validate-features
 description: Validate feature folder consistency across project folders. Detects orphaned features, missing FEATURE.md, and auto-repairs discrepancies. Use for periodic health checks of living docs structure.
 ---
 
@@ -101,7 +101,7 @@ Linked increment: {incrementId} ({exists/not found})
 
 {if discrepancies > 0 && !repair}
 To auto-repair these discrepancies:
-  /specweave:validate-features --repair
+  /sw:validate-features --repair
 
 This will:
   • Create missing project folders
@@ -135,7 +135,7 @@ Options:
 
 ### Example 1: Check for discrepancies
 ```
-User: /specweave:validate-features
+User: /sw:validate-features
 
 Output:
 ═══════════════════════════════════════════════════════
@@ -157,13 +157,13 @@ Linked increment: 0062-test-living-docs-auto-sync (not found)
 
 ───────────────────────────────────────────────────────
 
-🎯 To repair: /specweave:validate-features --repair
+🎯 To repair: /sw:validate-features --repair
 ═══════════════════════════════════════════════════════
 ```
 
 ### Example 2: Auto-repair discrepancies
 ```
-User: /specweave:validate-features --repair
+User: /sw:validate-features --repair
 
 Output:
 ═══════════════════════════════════════════════════════
@@ -203,6 +203,6 @@ Discrepancies found: 1
 
 ## RELATED COMMANDS
 
-- `/specweave:sync-specs` - Sync increment to living docs (includes consistency check)
-- `/specweave:validate` - Validate increment structure
-- `/specweave:archive` - Archive completed increments
+- `/sw:sync-specs` - Sync increment to living docs (includes consistency check)
+- `/sw:validate` - Validate increment structure
+- `/sw:archive` - Archive completed increments

package/plugins/specweave/commands/{specweave-validate.md → validate.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:validate
+name: sw:validate
 description: Validate SpecWeave increment with rule-based checks and optional AI quality assessment
 ---
 
@@ -10,7 +10,7 @@ You are helping the user validate a SpecWeave increment with optional AI-powered
 ## Usage
 
 ```bash
-/specweave:validate <increment-id> [--quality] [--export] [--fix] [--always]
+/sw:validate <increment-id> [--quality] [--export] [--fix] [--always]
 ```
 
 ## Arguments
@@ -68,7 +68,7 @@ This command implements a **two-gate validation system**:
 ### Step 1: Parse and Validate Arguments
 
 1. **Extract increment ID**:
-   - Parse from command: `/specweave:validate 001` → "001"
+   - Parse from command: `/sw:validate 001` → "001"
    - Normalize to 4-digit format: "0001"
    - Support formats: "1", "01", "001", "0001"
 
@@ -92,7 +92,7 @@ Available increments:
   • 0003-payment-processing
   • 0004-reporting-dashboard
 
-Usage: /specweave:validate-increment <id> [--quality] [--export] [--fix] [--always]
+Usage: /sw:validate-increment <id> [--quality] [--export] [--fix] [--always]
 ```
 
 ### Step 1.5: Sync AC Status (NEW - v0.33.0)
@@ -263,7 +263,7 @@ Action required:
 3. 🔴 FIX AC COVERAGE ERRORS (v0.23.0 - US-Task Linkage):
    - Create tasks for 4 uncovered ACs (AC-US2-03, AC-US3-01, AC-US3-05, AC-US4-02)
    - Add **Satisfies ACs** field to 2 orphan tasks (T-008, T-015)
-   - Run: /specweave:validate 0001 to verify 100% coverage
+   - Run: /sw:validate 0001 to verify 100% coverage
 4. Fix missing acceptance criteria for US-003
 5. Address "real-time updates" in plan.md or remove from spec.md
 6. Consider breaking down T012 into smaller tasks
@@ -591,7 +591,7 @@ To disable:
   1. Initialize your project
   2. Set validation.quality_judge.always_run: false
 
-Or run: /specweave:validate-increment <id> (quality will run automatically)
+Or run: /sw:validate-increment <id> (quality will run automatically)
 ```
 
 ### Step 8: Generate Validation Report
@@ -604,7 +604,7 @@ Or run: /specweave:validate-increment <id> (quality will run automatically)
 # Validation Report: Increment 0001-authentication
 
 Generated: 2025-10-28 14:32:15 UTC
-Command: /specweave:validate-increment 001 --quality
+Command: /sw:validate-increment 001 --quality
 
 ## Executive Summary
 
@@ -707,7 +707,7 @@ Command: /specweave:validate-increment 001 --quality
 
 | Date | Rule-Based | Quality Score | Command |
 |------|------------|---------------|---------|
-| 2025-10-28 | 120/120 | 87/100 | /specweave:validate-increment 001 --quality |
+| 2025-10-28 | 120/120 | 87/100 | /sw:validate-increment 001 --quality |
 | 2025-10-25 | 115/120 | N/A | Auto-validation on save |
 | 2025-10-24 | 110/120 | N/A | Auto-validation on save |
 
@@ -728,7 +728,7 @@ For details: .specweave/docs/internal/delivery/guides/increment-validation.md
 ### Example 1: Basic Validation (Rule-Based Only)
 
 ```bash
-/specweave:validate 001
+/sw:validate 001
 ```
 
 **Output**:
@@ -741,7 +741,7 @@ For details: .specweave/docs/internal/delivery/guides/increment-validation.md
 ### Example 2: Validation with Quality Assessment
 
 ```bash
-/specweave:validate 001 --quality
+/sw:validate 001 --quality
 ```
 
 **Output**:
@@ -758,7 +758,7 @@ Suggestions: 3 (2 high, 1 medium)
 ### Example 3: Validate and Export Suggestions
 
 ```bash
-/specweave:validate 001 --quality --export
+/sw:validate 001 --quality --export
 ```
 
 **Output**:
@@ -775,7 +775,7 @@ Suggestions: 3 (2 high, 1 medium)
 ### Example 4: Auto-Fix Issues
 
 ```bash
-/specweave:validate 001 --quality --fix
+/sw:validate 001 --quality --fix
 ```
 
 **Output**:
@@ -796,7 +796,7 @@ Re-validated: 92/100 (improvement: +5)
 ### Example 5: Make Quality Assessment Default
 
 ```bash
-/specweave:validate 001 --always
+/sw:validate 001 --always
 ```
 
 **Output**:
@@ -818,7 +818,7 @@ Available increments:
   • 0002-core-enhancements
   • 0003-payment-processing
 
-Usage: /specweave:validate-increment <id> [--quality] [--export] [--fix] [--always]
+Usage: /sw:validate-increment <id> [--quality] [--export] [--fix] [--always]
 ```
 
 ### Invalid Flags
@@ -831,7 +831,7 @@ Valid flags:
   --fix       Auto-fix issues (experimental)
   --always    Make quality assessment default
 
-Usage: /specweave:validate-increment <id> [--quality] [--export] [--fix] [--always]
+Usage: /sw:validate-increment <id> [--quality] [--export] [--fix] [--always]
 ```
 
 ### Quality Assessment Failed
@@ -841,7 +841,7 @@ Usage: /specweave:validate-increment <id> [--quality] [--export] [--fix] [--alwa
 ✅ Rule-based validation completed successfully (120/120)
 
 You can:
-  1. Try again: /specweave:validate-increment 001 --quality
+  1. Try again: /sw:validate-increment 001 --quality
   2. Continue with rule-based results
   3. Check logs: .specweave/increments/0001-name/logs/validation.log
 ```
@@ -862,7 +862,7 @@ Export suggestions to tasks? [Y/n]: _
 
 This command can be triggered by:
 
-1. **Manual execution**: `/specweave:validate 001 --quality`
+1. **Manual execution**: `/sw:validate 001 --quality`
 2. **Post-document-save hook**: Auto-runs rule-based validation
 3. **Pre-implementation hook**: Validates before starting tasks
 4. **CI/CD pipeline**: Automated validation in GitHub Actions
@@ -877,7 +877,7 @@ if [[ "$FILE" =~ spec\.md|plan\.md|tasks\.md|tests\.md ]]; then
   INCREMENT_ID=$(echo "$FILE" | grep -oP '(?<=increments/)\d{4}')
 
   # Run validation (rule-based only, no quality unless config says so)
-  /specweave:validate-increment "$INCREMENT_ID"
+  /sw:validate-increment "$INCREMENT_ID"
 fi
 ```
 
@@ -888,7 +888,7 @@ All validation settings use sensible defaults. Quality assessment is prompted ea
 ## Related Commands
 
 - `/create-increment`: Create new increment (auto-validates on creation)
-- `/specweave:sync-docs`: Review strategic documentation before implementation
+- `/sw:sync-docs`: Review strategic documentation before implementation
 - `/close-increment`: Close increment (validates before closing)
 - `/sync-github`: Sync to GitHub (validates before sync)
 
@@ -902,6 +902,6 @@ All validation settings use sensible defaults. Quality assessment is prompted ea
 
 **Important**: This command works alongside intent-based validation. Users can say:
 - "Validate quality of increment 001" (intent-based)
-- `/specweave:validate 001 --quality` (slash command)
+- `/sw:validate 001 --quality` (slash command)
 
 Both routes activate the same validation logic for consistency.

package/plugins/specweave/commands/{specweave-workflow.md → workflow.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:workflow
+name: sw:workflow
 description: Smart workflow navigator - shows current phase, reviews spec/tasks, suggests next step (validate, close, sync). Shows external tool status.
 ---
 
@@ -12,7 +12,7 @@ You are helping the user navigate through the SpecWeave increment workflow with
 ## Usage
 
 ```bash
-/specweave:workflow [increment-id]
+/sw:workflow [increment-id]
 ```
 
 **No arguments**: Auto-detects active increment
@@ -128,7 +128,7 @@ CURRENT PHASE: REVIEW_READY
 You're in the PLANNING phase. Tasks need to be generated.
 
 SUGGESTED ACTION:
-  Run: /specweave:plan 0053
+  Run: /sw:plan 0053
 
 This will:
   • Generate plan.md with architecture design
@@ -149,7 +149,7 @@ CURRENT TASK: T-024 - Implement soft delete mechanism
   Satisfies: AC-US3-01, AC-US3-02
 
 SUGGESTED ACTION:
-  Continue: /specweave:do 0053
+  Continue: /sw:do 0053
 
 PROGRESS:
   Estimated remaining: ~4-6 hours
@@ -176,14 +176,14 @@ SUGGESTED ACTIONS (in order):
      cat .specweave/increments/0053-*/tasks.md | head -100
 
   2. VALIDATE QUALITY:
-     /specweave:validate 0053 --quality
+     /sw:validate 0053 --quality
 
   3. IF VALIDATION PASSES:
-     /specweave:done 0053
+     /sw:done 0053
 
 Quick commands:
-  • /specweave:progress       - See task breakdown
-  • /specweave:check-tests 0053 - Verify test coverage
+  • /sw:progress       - See task breakdown
+  • /sw:check-tests 0053 - Verify test coverage
 ```
 
 ### Phase: VALIDATE_READY
@@ -194,7 +194,7 @@ Quick commands:
 Ready for validation. Run quality checks before closing.
 
 SUGGESTED ACTION:
-  Run: /specweave:validate 0053 --quality
+  Run: /sw:validate 0053 --quality
 
 This will check:
   • 141 rule-based validation checks
@@ -203,7 +203,7 @@ This will check:
   • Three-file canonical structure (ADR-0047)
 
 After validation passes:
-  Run: /specweave:done 0053
+  Run: /sw:done 0053
 ```
 
 ### Phase: CLOSE_READY
@@ -219,7 +219,7 @@ VALIDATION SUMMARY:
   Quality score: 87/100 (GOOD) ✅
 
 SUGGESTED ACTION:
-  Run: /specweave:done 0053
+  Run: /sw:done 0053
 
 This will:
   • Run PM validation (3 gates: tasks, tests, docs)
@@ -241,7 +241,7 @@ After closure:
 Increment closed! Sync to external tools pending.
 
 SUGGESTED ACTION:
-  Run: /specweave:sync-progress 0053
+  Run: /sw:sync-progress 0053
 
 This will sync to:
   ✅ Living docs (user stories, features)
@@ -250,8 +250,8 @@ This will sync to:
   ⚪ ADO (not configured)
 
 Or sync individually:
-  • /specweave:sync-specs 0053  - Living docs only
-  • /specweave-github:close-issue 0053 - GitHub only
+  • /sw:sync-specs 0053  - Living docs only
+  • /sw-github:close-issue 0053 - GitHub only
 ```
 
 ### Phase: COMPLETED
@@ -271,11 +271,11 @@ EXTERNAL TOOLS STATUS:
   Living docs: Synced ✅
 
 WHAT'S NEXT:
-  • Start new increment: /specweave:increment "feature name"
-  • Check backlog: /specweave:status
-  • Archive this increment: /specweave:archive 0053
+  • Start new increment: /sw:increment "feature name"
+  • Check backlog: /sw:status
+  • Archive this increment: /sw:archive 0053
 
-Quick: /specweave:next (auto-suggests next work)
+Quick: /sw:next (auto-suggests next work)
 ```
 
 ---
@@ -297,7 +297,7 @@ async function showExternalToolsStatus(metadata) {
     console.log(`    Last sync: ${metadata.github.lastSync || 'Not synced'}`);
   } else {
     console.log('  GitHub: ⚪ Not linked');
-    console.log('    Setup: /specweave-github:create-issue 0053');
+    console.log('    Setup: /sw-github:create-issue 0053');
   }
 
   // JIRA
@@ -332,10 +332,10 @@ async function showExternalToolsStatus(metadata) {
     URL: https://github.com/org/repo/issues/142
     Last sync: 2025-11-25 09:15:00
 
-    Action needed: Run /specweave:sync-progress to update
+    Action needed: Run /sw:sync-progress to update
 
   JIRA: ⚪ Not configured
-    Setup: /specweave-jira:sync to connect
+    Setup: /sw-jira:sync to connect
 
   Azure DevOps: ⚪ Not configured
 ```
@@ -358,7 +358,7 @@ async function showExternalToolsStatus(metadata) {
     US-003: Cascade delete child items        [PENDING] 🔵
     US-004: Audit log for deletions           [PENDING] 🔵
 
-  Action: Run /specweave:sync-specs 0053 to update living docs
+  Action: Run /sw:sync-specs 0053 to update living docs
 ```
 
 ---
@@ -402,7 +402,7 @@ CURRENT PHASE: REVIEW_READY
   GitHub Issue #142:
     Status: open 🔵
     Checklist: 35/37 tasks checked
-    Action: Will auto-close after /specweave:done
+    Action: Will auto-close after /sw:done
 
   JIRA: ⚪ Not configured
   ADO:  ⚪ Not configured
@@ -421,16 +421,16 @@ All tasks complete! Recommended workflow:
      Review spec.md and tasks.md for completeness
 
   2. VALIDATE:
-     /specweave:validate 0053 --quality
+     /sw:validate 0053 --quality
 
   3. CLOSE (if validation passes):
-     /specweave:done 0053
+     /sw:done 0053
 
   4. SYNC (automatic after close):
      Living docs and GitHub will auto-sync
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Quick: /specweave:workflow (refresh) | /specweave:next (auto-transition)
+Quick: /sw:workflow (refresh) | /sw:next (auto-transition)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -443,9 +443,9 @@ Quick: /specweave:workflow (refresh) | /specweave:next (auto-transition)
 ❌ No active increment found.
 
 Options:
-  • Check status: /specweave:status
-  • Start new: /specweave:increment "feature name"
-  • Resume paused: /specweave:resume <id>
+  • Check status: /sw:status
+  • Start new: /sw:increment "feature name"
+  • Resume paused: /sw:resume <id>
 
 Available increments:
   0052-feature-a (paused)
@@ -460,24 +460,24 @@ Available increments:
   0052-feature-a (in-progress)
   0053-feature-b (completed)
 
-Usage: /specweave:workflow [increment-id]
+Usage: /sw:workflow [increment-id]
 ```
 
 ---
 
 ## Related Commands
 
-- `/specweave:progress` - Quick task completion view
-- `/specweave:validate` - Quality validation
-- `/specweave:done` - Close increment
-- `/specweave:sync-progress` - Sync to external tools
-- `/specweave:next` - Auto-transition to next work
-- `/specweave:status` - Overview of all increments
+- `/sw:progress` - Quick task completion view
+- `/sw:validate` - Quality validation
+- `/sw:done` - Close increment
+- `/sw:sync-progress` - Sync to external tools
+- `/sw:next` - Auto-transition to next work
+- `/sw:status` - Overview of all increments
 
 ---
 
-**Key difference from `/specweave:next`**:
-- `/specweave:workflow` = **Informational dashboard** (where am I? what's next?)
-- `/specweave:next` = **Action-oriented** (auto-close and transition)
+**Key difference from `/sw:next`**:
+- `/sw:workflow` = **Informational dashboard** (where am I? what's next?)
+- `/sw:next` = **Action-oriented** (auto-close and transition)
 
-Use `/specweave:workflow` to **understand your position**, then use specific commands to act.
+Use `/sw:workflow` to **understand your position**, then use specific commands to act.

package/plugins/specweave/hooks/README.md

@@ -23,7 +23,7 @@ Core hooks automate SpecWeave's fundamental workflows:
 **Triggers**: BEFORE user's command executes (prompt-based hook)
 
 **Actions** (Zero-Token Validation):
-1. **Discipline enforcement** - Blocks `/specweave:increment` if incomplete increments exist
+1. **Discipline enforcement** - Blocks `/sw:increment` if incomplete increments exist
 2. **Context injection** - Adds active increment status to every prompt
 3. **Command suggestions** - Guides users to SpecWeave commands
 
@@ -199,7 +199,7 @@ Hooks are configured via `.specweave/config.json` (created automatically during
 - `external_tracker_sync: true` - Syncs progress to GitHub/Jira/ADO (requires sync profile configured)
 
 **post-increment-planning**:
-- `auto_create_issue: true` - Automatically creates GitHub issue after `/specweave:increment` completes
+- `auto_create_issue: true` - Automatically creates GitHub issue after `/sw:increment` completes
 
 ### Sound Notifications
 
@@ -260,7 +260,7 @@ bash -n plugins/specweave-github/hooks/post-task-completion.sh
 ```
 
 ### Test Integrated Workflow
-1. Create increment: `/specweave:increment "test feature"`
+1. Create increment: `/sw:increment "test feature"`
 2. Complete a task (via TodoWrite)
 3. Check logs: `tail -f .specweave/logs/hooks-debug.log`
 4. Verify hook execution in logs
@@ -405,8 +405,8 @@ bash -n plugins/specweave-ado/hooks/post-task-completion.sh
 ```
 
 **Test integrated workflow**:
-1. Create increment: `/specweave:increment "test"`
-2. Create GitHub issue: `/specweave-github:create-issue 0001`
+1. Create increment: `/sw:increment "test"`
+2. Create GitHub issue: `/sw-github:create-issue 0001`
 3. Complete a task (TodoWrite)
 4. Check logs: `tail -f .specweave/logs/hooks-debug.log`
 5. Verify:

package/plugins/specweave/hooks/config-env-separator.sh

@@ -0,0 +1,99 @@
+#!/usr/bin/env bash
+#
+# Pre-Tool-Use Hook: Config-Env Separator
+#
+# Blocks Write/Edit to src/ files that read config values from process.env
+# Configuration (domain, org, project) should come from ConfigManager (config.json)
+# Only secrets (PAT, tokens, emails) should use process.env
+#
+# Ref: ADR-0194 - Enforce Config JSON Separation
+#
+
+set -e
+
+# Only run for Write and Edit tools
+if [[ "$TOOL_NAME" != "Write" ]] && [[ "$TOOL_NAME" != "Edit" ]]; then
+  exit 0
+fi
+
+# Parse tool input
+FILE_PATH=$(echo "$TOOL_INPUT" | jq -r '.file_path // empty')
+CONTENT=$(echo "$TOOL_INPUT" | jq -r '.content // .new_string // empty')
+
+# Skip if no file path
+if [[ -z "$FILE_PATH" ]]; then
+  exit 0
+fi
+
+# Only check src/ files (not tests, plugins, etc.)
+if [[ ! "$FILE_PATH" =~ /src/ ]]; then
+  exit 0
+fi
+
+# Skip test files
+if [[ "$FILE_PATH" =~ \.test\.ts$ ]]; then
+  exit 0
+fi
+
+# Skip spec files
+if [[ "$FILE_PATH" =~ \.spec\.ts$ ]]; then
+  exit 0
+fi
+
+# Config variables that should NOT be in process.env
+CONFIG_VARS=(
+  "JIRA_DOMAIN"
+  "JIRA_BASE_URL"
+  "AZURE_DEVOPS_ORG"
+  "AZURE_DEVOPS_PROJECT"
+  "GITHUB_OWNER"
+  "GITHUB_REPO"
+  "ADO_ORG_URL"
+  "ADO_PROJECT"
+)
+
+# Check for violations
+VIOLATIONS=""
+for VAR in "${CONFIG_VARS[@]}"; do
+  if echo "$CONTENT" | grep -q "process\.env\.$VAR"; then
+    VIOLATIONS="$VIOLATIONS\n  - process.env.$VAR"
+  fi
+done
+
+# If violations found, block the operation
+if [[ -n "$VIOLATIONS" ]]; then
+  echo ""
+  echo "-------------------------------------------------------------------"
+  echo "BLOCKED: Configuration values MUST use ConfigManager, not process.env"
+  echo "-------------------------------------------------------------------"
+  echo ""
+  echo "File: $FILE_PATH"
+  echo ""
+  echo "Violations detected:"
+  echo -e "$VIOLATIONS"
+  echo ""
+  echo "CORRECT PATTERN:"
+  echo "  const config = await this.configManager.read();"
+  echo "  const domain = config.issueTracker?.domain || '';"
+  echo "  const org = config.issueTracker?.organization_ado || '';"
+  echo ""
+  echo "FORBIDDEN PATTERN:"
+  echo "  const domain = process.env.JIRA_DOMAIN;  // VIOLATION!"
+  echo "  const org = process.env.AZURE_DEVOPS_ORG;  // VIOLATION!"
+  echo ""
+  echo "Ref: ADR-0194, CLAUDE.md Configuration section"
+  echo ""
+  echo "To bypass (EMERGENCY ONLY): SPECWEAVE_SKIP_CONFIG_CHECK=1"
+  echo "-------------------------------------------------------------------"
+  echo ""
+
+  # Allow bypass for emergencies
+  if [[ "$SPECWEAVE_SKIP_CONFIG_CHECK" == "1" ]]; then
+    echo "WARNING: SPECWEAVE_SKIP_CONFIG_CHECK=1 - Bypassing config check!"
+    exit 0
+  fi
+
+  exit 1
+fi
+
+exit 0