specweave 0.17.13 → 0.17.15

package/CLAUDE.md

@@ -1720,6 +1720,359 @@ SPEC-002: Intelligent AI Capabilities (Living Docs - Permanent, Feature-Level)
 
 ---
 
+## Enterprise Specs Organization (Domain-Based)
+
+**NEW in v0.20.0**: Living docs specs organized by feature domain with rich metadata and auto-generated indices.
+
+### The Problem with Flat Structure
+
+**Before** (v0.19.x and earlier):
+```
+.specweave/docs/internal/specs/default/
+├── spec-001-core-framework-architecture.md
+├── spec-002-intelligent-capabilities.md
+├── spec-003-developer-experience.md
+... (30+ files in one folder)
+├── nfr-risks.md
+├── nfr-configuration-example.md
+├── overview-overview.md
+└── us-us1-single-provider-setup.md
+```
+
+**Problems**:
+- ❌ 30+ files in single folder (hard to navigate)
+- ❌ Mixed document types (specs, NFRs, overviews, user stories)
+- ❌ No categorization by feature area
+- ❌ Poor scalability (becomes unmanageable at 100+ specs)
+- ❌ No rich metadata (status, priority, ownership)
+
+### Enterprise Solution: Domain-Based Organization
+
+**After** (v0.20.0+):
+```
+.specweave/docs/internal/specs/default/
+├── core-framework/              # Domain folder
+│   ├── README.md                # Domain overview
+│   ├── spec-001-*.md           # Feature specs
+│   ├── spec-004-*.md
+│   ├── nfrs/                    # NFRs for this domain
+│   │   └── nfr-cross-platform.md
+│   └── user-stories/            # Extracted user stories
+│       └── us-001-*.md
+│
+├── developer-experience/
+│   ├── spec-003-*.md
+│   ├── spec-022-*.md
+│   └── user-stories/
+│
+├── integrations/
+│   ├── github/
+│   │   └── spec-017-sync-fix.md
+│   ├── jira/
+│   └── ado/
+│
+├── infrastructure/
+│   ├── spec-004-metrics.md
+│   ├── spec-029-cicd-failure.md
+│   └── nfrs/
+│
+├── quality-velocity/
+│   ├── spec-005-stabilization.md
+│   └── spec-010-dora-metrics.md
+│
+├── intelligence/
+│   ├── spec-002-intelligent-capabilities.md
+│   ├── spec-016-self-reflection.md
+│   └── spec-009-intelligent-reopen.md
+│
+└── _index/                      # Auto-generated indices
+    ├── README.md                # Master index
+    ├── by-status.md             # Active, planning, completed, archived
+    ├── by-domain.md             # All domains
+    ├── by-release.md            # 1.0.0, 1.1.0, 2.0.0
+    ├── by-priority.md           # P0, P1, P2, P3
+    └── by-team.md               # Core Team, Platform Team, etc.
+```
+
+### Six Feature Domains
+
+| Domain | Description | Examples |
+|--------|-------------|----------|
+| **core-framework** | Core framework capabilities | CLI, plugin architecture, configuration, lifecycle |
+| **developer-experience** | DX improvements | Setup, onboarding, docs, error messages, usability |
+| **integrations** | External tool integrations | GitHub, JIRA, Azure DevOps, Figma, Slack |
+| **infrastructure** | Platform, DevOps, ops | CI/CD, monitoring, observability, performance |
+| **quality-velocity** | Testing, metrics, releases | Testing framework, DORA metrics, stabilization |
+| **intelligence** | AI-powered features | Model selection, self-reflection, smart workflows |
+
+### Rich Metadata for Every Spec
+
+Every spec gets YAML frontmatter with comprehensive metadata:
+
+```yaml
+---
+# Identity
+id: spec-001-core-framework-architecture
+title: "Core Framework & Architecture"
+version: 2.0
+status: active | planning | completed | archived
+
+# Classification
+domain: core-framework
+category: feature | nfr | user-story | overview
+priority: P0 | P1 | P2 | P3
+complexity: low | medium | high | very-high
+
+# Ownership
+team: Core Team
+owner: @anton-abyzov
+stakeholders: ["Product", "Engineering"]
+
+# Lifecycle
+created: 2025-01-15
+last_updated: 2025-11-10
+target_release: 1.0.0
+
+# Relationships
+increments: [0001, 0002, 0004, 0005]
+depends_on: []
+blocks: [spec-002, spec-003]
+related: [spec-016]
+
+# External Links
+github_project: https://github.com/anton-abyzov/specweave/projects/1
+jira_epic: null
+confluence: null
+
+# Tags
+tags: [framework, cli, plugin-system, mvp]
+
+# Metrics
+estimated_effort: 120h
+actual_effort: 95h
+user_stories: 35
+completion: 100%
+---
+```
+
+### Auto-Generated Navigation Indices
+
+**Five index views** for different navigation needs:
+
+1. **by-status.md** - Status-based view
+   - Active (currently being worked on)
+   - Planning (being planned)
+   - Completed (delivered to production)
+   - Archived (historical reference)
+
+2. **by-domain.md** - Domain-based view
+   - Core Framework (5 specs)
+   - Developer Experience (3 specs)
+   - Integrations (4 specs)
+   - Infrastructure (3 specs)
+   - Quality & Velocity (2 specs)
+   - Intelligence (3 specs)
+
+3. **by-release.md** - Release planning view
+   - 1.0.0 (MVP release)
+   - 1.1.0 (Post-launch improvements)
+   - 2.0.0 (Major features)
+   - Unscheduled (backlog)
+
+4. **by-priority.md** - Priority-based view
+   - P0 (Critical, security, production blockers)
+   - P1 (High, MVPessential, core features)
+   - P2 (Medium, nice-to-have, enhancements)
+   - P3 (Low, future, backlog, deferred)
+
+5. **by-team.md** - Team ownership view
+   - Core Team
+   - Platform Team
+   - DX Team
+   - Integrations Team
+
+### Automated Classification
+
+**Intelligent Living Docs Sync** auto-classifies specs by domain using keyword matching:
+
+```typescript
+// Auto-classification during living docs sync
+const classifyDomain = (spec: string): string => {
+  const keywords = {
+    'core-framework': ['framework', 'cli', 'plugin', 'core', 'foundation'],
+    'developer-experience': ['dx', 'ux', 'installation', 'setup', 'guide'],
+    'integrations': ['github', 'jira', 'ado', 'figma', 'sync'],
+    'infrastructure': ['cicd', 'monitoring', 'observability', 'performance'],
+    'quality-velocity': ['testing', 'dora', 'metrics', 'stabilization'],
+    'intelligence': ['ai', 'intelligent', 'smart', 'reflection', 'model']
+  };
+
+  // Score each domain and return highest
+  // Confidence threshold: 0.5 (50% keyword match)
+};
+```
+
+### PM Agent Instructions
+
+**CRITICAL**: When creating living docs specs, PM agent MUST:
+
+1. **Classify Domain** - Determine feature domain based on content
+2. **Add Rich Metadata** - Include all required frontmatter fields
+3. **Use Correct Path** - Save to domain-specific folder
+4. **Generate README** - Update domain README.md
+5. **Regenerate Indices** - Run index generation after creating spec
+
+**Example PM Agent Workflow**:
+
+```typescript
+// Step 1: Classify domain
+const domain = classifyDomain(spec.title, spec.content);
+// Result: "core-framework"
+
+// Step 2: Determine path
+const specPath = `.specweave/docs/internal/specs/default/${domain}/spec-001-core-framework.md`;
+
+// Step 3: Add frontmatter
+const frontmatter = {
+  id: 'spec-001-core-framework-architecture',
+  title: 'Core Framework & Architecture',
+  domain: 'core-framework',
+  category: 'feature',
+  priority: 'P1',
+  status: 'active',
+  team: 'Core Team',
+  owner: '@anton-abyzov',
+  created: '2025-11-12',
+  target_release: '1.0.0',
+  tags: ['framework', 'cli', 'plugin']
+};
+
+// Step 4: Write spec with frontmatter
+writeSpec(specPath, frontmatter, content);
+
+// Step 5: Update domain README
+updateDomainReadme(domain, spec);
+
+// Step 6: Regenerate indices
+regenerateIndices();
+```
+
+### Migration Scripts
+
+**Three scripts for migration**:
+
+1. **Classify Specs** (`scripts/classify-specs.ts`)
+   - Scans existing specs
+   - Auto-classifies by domain (keyword matching)
+   - Generates classification report
+   - Saves classification.json for migration
+
+2. **Migrate to Domains** (`scripts/migrate-specs-to-domains.ts`)
+   - Reads classification.json
+   - Creates domain folders
+   - Moves specs to domain-specific folders
+   - Adds/updates frontmatter
+   - Creates domain READMEs
+   - Supports --dry-run mode
+
+3. **Generate Indices** (`scripts/generate-spec-indices.ts`)
+   - Scans all specs
+   - Generates 5 navigation indices
+   - Creates master index (README.md)
+   - Shows statistics
+
+**Usage**:
+
+```bash
+# Step 1: Classify existing specs
+npx ts-node scripts/classify-specs.ts
+# Output: classification-report.md, classification.json
+
+# Step 2: Review classification
+vim .specweave/docs/internal/specs/default/_index/classification-report.md
+
+# Step 3: Migrate (dry-run first)
+npx ts-node scripts/migrate-specs-to-domains.ts --dry-run
+
+# Step 4: Migrate (actual)
+npx ts-node scripts/migrate-specs-to-domains.ts
+
+# Step 5: Generate indices
+npx ts-node scripts/generate-spec-indices.ts
+```
+
+### Benefits
+
+**For Users**:
+- ✅ Find specs 10x faster (browse by domain vs scroll through 30+ files)
+- ✅ Clear relationships (dependencies, blockers, related specs)
+- ✅ Rich metadata (status, priority, ownership, effort)
+- ✅ Multi-dimensional navigation (status, domain, release, team, priority)
+
+**For Teams**:
+- ✅ Team ownership (core-team/, platform-team/)
+- ✅ Release planning (1.0.0, 1.1.0, 2.0.0)
+- ✅ Dependency management (blocks[], depends_on[])
+- ✅ Effort tracking (estimated_effort vs actual_effort)
+
+**For Enterprise**:
+- ✅ Scalability (handles 100+ specs easily)
+- ✅ Compliance (audit trail via metadata)
+- ✅ Reporting (auto-generated indices for stakeholders)
+- ✅ Multi-project (backend/, frontend/, mobile/)
+
+### Configuration
+
+Add to `.specweave/config.json`:
+
+```json
+{
+  "specs": {
+    "organization": {
+      "strategy": "domain-based",
+      "autoDomainClassification": true,
+      "autoGenerateIndices": true,
+      "requireMetadata": true,
+      "domains": [
+        "core-framework",
+        "developer-experience",
+        "integrations",
+        "infrastructure",
+        "quality-velocity",
+        "intelligence"
+      ],
+      "metadata": {
+        "required": ["id", "title", "status", "domain", "team", "owner"],
+        "optional": ["priority", "complexity", "tags", "increments"]
+      }
+    }
+  }
+}
+```
+
+### For Agents and Skills
+
+**PM Agent MUST**:
+1. Always classify domain before creating spec
+2. Add rich frontmatter with all required fields
+3. Save to correct domain folder (not flat structure)
+4. Update domain README after creating spec
+5. Regenerate indices after spec creation
+
+**Living Docs Sync MUST**:
+1. Detect domain from increment spec content
+2. Place spec in correct domain folder
+3. Add/update frontmatter with metadata
+4. Preserve existing classification if present
+5. Regenerate indices after sync
+
+**See**:
+- [Organization Strategy](.specweave/docs/internal/specs/ORGANIZATION-STRATEGY.md) - Complete architecture
+- Migration scripts in `scripts/` directory
+- Configuration in `.specweave/config.json`
+
+---
+
 ## Living Completion Reports
 
 ### The Problem with Traditional Reports
@@ -2558,6 +2911,109 @@ cat .specweave/increments/0016-self-reflection-system/metadata.json
 
 ---
 
+**✅ Metadata Validation & Fallback Creation** (NEW in v0.14.0+):
+
+**The Problem**: Hook failures (no GitHub CLI, network issues, permission problems) left increments without metadata.json, breaking status line, WIP limits, and external sync.
+
+**The Solution**: Multi-layer validation ensures 100% metadata.json coverage.
+
+**How It Works**:
+
+**Layer 1: Hook Fallback** (Automatic)
+- After GitHub issue creation (success or fail)
+- Hook validates metadata.json exists
+- If missing → creates minimal metadata automatically
+- User sees warning + manual fix instructions
+
+```bash
+# Hook output example (GitHub CLI not found):
+🔗 Checking GitHub issue auto-creation...
+  ⚠️  GitHub CLI (gh) not found, skipping issue creation
+
+🔍 Validating metadata.json existence...
+  ⚠️  metadata.json not found (hook may have failed)
+  📝 Creating minimal metadata as fallback...
+  ✅ Created minimal metadata.json
+  ⚠️  Note: No GitHub issue linked
+  💡 Run /specweave-github:create-issue 0023-feature to create one manually
+```
+
+**Layer 2: PM Agent Validation** (Automatic)
+- PM agent checks metadata.json after creating spec/plan/tasks
+- If missing → creates minimal metadata + warns user
+- Shows GitHub issue status (linked or not)
+
+```markdown
+✅ Increment validation passed - metadata.json exists
+   ✅ GitHub issue #45 linked
+   🔗 https://github.com/anton-abyzov/specweave/issues/45
+```
+
+**Layer 3: Lazy Initialization** (Fallback)
+- `MetadataManager.read()` creates metadata on first access
+- Used by `/specweave:status`, `/pause`, `/resume` commands
+- Creates basic metadata but WITHOUT GitHub info
+
+**Minimal Metadata Format** (when GitHub fails):
+```json
+{
+  "id": "0023-release-management-enhancements",
+  "status": "active",
+  "type": "feature",
+  "created": "2025-11-11T15:43:00Z",
+  "lastActivity": "2025-11-11T15:43:00Z"
+}
+```
+
+**Full Metadata Format** (when GitHub succeeds):
+```json
+{
+  "id": "0016-self-reflection-system",
+  "status": "active",
+  "type": "feature",
+  "created": "2025-11-10T12:00:00Z",
+  "lastActivity": "2025-11-10T12:00:00Z",
+  "github": {
+    "issue": 30,
+    "url": "https://github.com/anton-abyzov/specweave/issues/30",
+    "synced": "2025-11-10T12:00:00Z"
+  },
+  "githubProfile": "specweave-dev"
+}
+```
+
+**Benefits**:
+- ✅ **100% coverage**: Every increment gets metadata.json (no silent failures)
+- ✅ **Immediate feedback**: User knows if GitHub issue creation failed
+- ✅ **Graceful degradation**: Creates minimal metadata as fallback
+- ✅ **Clear next steps**: Shows manual fix command if needed
+- ✅ **Status line works**: Even without GitHub integration
+- ✅ **WIP limits work**: Counts active increments correctly
+
+**Configuration Note**:
+
+The old config key `hooks.post_increment_planning.auto_create_github_issue` is **deprecated** (v0.14.0+).
+
+```json
+{
+  "hooks": {
+    "post_increment_planning": {
+      // ❌ REMOVED (deprecated)
+      // "auto_create_github_issue": false
+    }
+  },
+  "sync": {
+    "settings": {
+      "autoCreateIssue": true  // ✅ Use this instead
+    }
+  }
+}
+```
+
+**Single source of truth**: `sync.settings.autoCreateIssue`
+
+---
+
 ## Status Line Feature (Increment Progress Display)
 
 **NEW in v0.14.0**: Ultra-fast status line showing current increment progress with intelligent caching.

package/README.md

@@ -207,11 +207,12 @@ specweave init .
 
 ## Key Features
 
+- 📚 **Living Documentation** - Auto-updates after every task (no manual sync!)
 - 🧪 **Test-Aware Planning** - Embedded tests in BDD format (Given/When/Then)
 - 🎯 **Disciplined Progress** - Can't start increment N+1 until N is DONE
 - ⏸️ **Intelligent Pausing** - Auto-detects blockers, pauses with context, resumes when ready
-- 📚 **Living Documentation** - Auto-updates after every task (no manual sync!)
 - 🤖 **AI Agents** - PM, Architect, Quality Judge guide your work
+- 🔧 **CI/CD Auto-Fix** - Workflow failures auto-fixed by Claude (just mention `@claude`)
 - 🌍 **Multilingual** - Work in 11 languages (FREE translation)
 - 🏢 **Multi-Project** - Organize by team/repo/microservice
 - 🔗 **Issue Tracker Sync** - GitHub, Jira, Azure DevOps integration
@@ -220,6 +221,42 @@ specweave init .
 
 ---
 
+## 🔧 CI/CD Auto-Fix
+
+**Workflow fails? Claude fixes it automatically.**
+
+When any GitHub Actions workflow fails, SpecWeave automatically:
+1. Creates an issue mentioning `@claude`
+2. Claude analyzes the failure logs
+3. Claude creates a PR with the fix
+4. You review and merge
+5. Workflow re-runs and passes ✅
+
+**Manual Trigger**:
+```markdown
+@claude This workflow failed: https://github.com/your-org/repo/actions/runs/12345
+
+Please analyze the logs and create a fix PR.
+```
+
+**Automatic** (via GitHub Actions):
+- Detects failures automatically
+- No manual intervention needed
+- Works 24/7 in the cloud
+- Zero cost (uses GitHub Actions free tier)
+
+**Common fixes**:
+- TypeScript compilation errors
+- Test failures
+- Linting violations
+- Missing imports
+- Type mismatches
+- Configuration issues
+
+**[→ Setup Guide](https://spec-weave.com/docs/features/cicd-autofix)**
+
+---
+
 ## 📖 Documentation
 
 **Complete guides, tutorials, and API reference:**

package/dist/src/cli/commands/cicd-monitor.d.ts

@@ -0,0 +1,11 @@
+/**
+ * CI/CD Monitor CLI Command
+ *
+ * Command-line interface for starting/stopping/querying the CI/CD monitor.
+ */
+import { Command } from 'commander';
+/**
+ * Register cicd-monitor command
+ */
+export declare function registerCICDMonitorCommand(program: Command): void;
+//# sourceMappingURL=cicd-monitor.d.ts.map

package/dist/src/cli/commands/cicd-monitor.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cicd-monitor.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/cicd-monitor.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAkKpC;;GAEG;AACH,wBAAgB,0BAA0B,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CA0BjE"}

package/dist/src/cli/commands/cicd-monitor.js

@@ -0,0 +1,154 @@
+/**
+ * CI/CD Monitor CLI Command
+ *
+ * Command-line interface for starting/stopping/querying the CI/CD monitor.
+ */
+import { WorkflowMonitor } from '../../core/cicd/workflow-monitor';
+import { StateManager } from '../../core/cicd/state-manager';
+import { Notifier } from '../../core/cicd/notifier';
+import * as fs from 'fs-extra';
+import * as path from 'path';
+/**
+ * Load configuration from environment variables
+ */
+function loadConfig() {
+    return {
+        GITHUB_TOKEN: process.env.GITHUB_TOKEN,
+        GITHUB_OWNER: process.env.GITHUB_OWNER,
+        GITHUB_REPO: process.env.GITHUB_REPO,
+        CICD_POLL_INTERVAL: process.env.CICD_POLL_INTERVAL || '60000',
+        CICD_NOTIFICATION_CHANNELS: process.env.CICD_NOTIFICATION_CHANNELS || 'console,file',
+        CICD_WEBHOOK_URL: process.env.CICD_WEBHOOK_URL
+    };
+}
+/**
+ * Start CI/CD monitor
+ */
+async function startMonitor(options) {
+    const config = loadConfig();
+    // Validate required config
+    if (!config.GITHUB_TOKEN) {
+        console.error('❌ Error: GITHUB_TOKEN environment variable is required');
+        console.error('   Set it in .env or export GITHUB_TOKEN=<your-token>');
+        process.exit(1);
+    }
+    if (!config.GITHUB_OWNER || !config.GITHUB_REPO) {
+        console.error('❌ Error: GITHUB_OWNER and GITHUB_REPO are required');
+        console.error('   Set them in .env or pass as arguments');
+        process.exit(1);
+    }
+    // Override from CLI arguments
+    const owner = options.owner || config.GITHUB_OWNER;
+    const repo = options.repo || config.GITHUB_REPO;
+    const pollInterval = parseInt(options.interval || config.CICD_POLL_INTERVAL, 10);
+    console.log('🚀 Starting CI/CD Monitor...');
+    console.log(`   Repository: ${owner}/${repo}`);
+    console.log(`   Poll interval: ${pollInterval}ms (${pollInterval / 1000}s)`);
+    // Create state manager
+    const stateManager = new StateManager();
+    // Create notifier
+    const notificationChannels = config.CICD_NOTIFICATION_CHANNELS.split(',').filter((c) => c.trim());
+    const notifier = new Notifier({
+        channels: notificationChannels,
+        webhookUrl: config.CICD_WEBHOOK_URL,
+        debug: options.debug || false
+    });
+    // Create and start monitor
+    const monitor = new WorkflowMonitor({
+        token: config.GITHUB_TOKEN,
+        owner,
+        repo,
+        pollInterval,
+        debug: options.debug || false
+    }, stateManager);
+    monitor.start();
+    console.log('✅ Monitor started');
+    console.log('   Press Ctrl+C to stop');
+    // Handle graceful shutdown
+    process.on('SIGINT', () => {
+        console.log('\n⏹️  Stopping monitor...');
+        monitor.stop();
+        console.log('✅ Monitor stopped');
+        process.exit(0);
+    });
+    // Keep process alive
+    await new Promise(() => { });
+}
+/**
+ * Query monitor status
+ */
+async function queryStatus() {
+    const stateManager = new StateManager();
+    const state = await stateManager.loadState();
+    console.log('📊 CI/CD Monitor Status\n');
+    // Last poll
+    if (state.lastPoll) {
+        const lastPollDate = new Date(state.lastPoll);
+        const elapsed = Date.now() - lastPollDate.getTime();
+        console.log(`   Last poll: ${lastPollDate.toLocaleString()} (${Math.floor(elapsed / 1000)}s ago)`);
+    }
+    else {
+        console.log('   Last poll: Never');
+    }
+    // Failure statistics
+    console.log(`\n📈 Statistics:`);
+    console.log(`   Total failures detected: ${state.totalFailures}`);
+    console.log(`   Failures processed: ${state.totalProcessed}`);
+    console.log(`   Failures fixed: ${state.totalFixed}`);
+    // Unprocessed failures
+    const unprocessed = Object.values(state.failures).filter((f) => !f.processed);
+    console.log(`\n⏳ Unprocessed failures: ${unprocessed.length}`);
+    if (unprocessed.length > 0) {
+        console.log('\n   Recent unprocessed failures:');
+        unprocessed.slice(0, 5).forEach((failure) => {
+            console.log(`   • ${failure.workflowName} (run #${failure.runId})`);
+            console.log(`     Branch: ${failure.branch}`);
+            console.log(`     Detected: ${new Date(failure.detectedAt).toLocaleString()}`);
+            console.log(`     URL: ${failure.url}\n`);
+        });
+        if (unprocessed.length > 5) {
+            console.log(`   ... and ${unprocessed.length - 5} more`);
+        }
+    }
+}
+/**
+ * Clear monitor state (reset)
+ */
+async function clearState() {
+    const statePath = path.join(process.cwd(), '.specweave/state/cicd-monitor.json');
+    if (await fs.pathExists(statePath)) {
+        await fs.remove(statePath);
+        console.log('✅ State cleared');
+    }
+    else {
+        console.log('ℹ️  No state to clear');
+    }
+}
+/**
+ * Register cicd-monitor command
+ */
+export function registerCICDMonitorCommand(program) {
+    const monitorCmd = program
+        .command('cicd-monitor')
+        .description('CI/CD workflow monitoring and auto-fix');
+    // Start monitor
+    monitorCmd
+        .command('start')
+        .description('Start monitoring GitHub Actions workflows')
+        .option('-o, --owner <owner>', 'GitHub repository owner')
+        .option('-r, --repo <repo>', 'GitHub repository name')
+        .option('-i, --interval <ms>', 'Poll interval in milliseconds (default: 60000)')
+        .option('-d, --debug', 'Enable debug logging')
+        .action(startMonitor);
+    // Query status
+    monitorCmd
+        .command('status')
+        .description('Show monitor status and statistics')
+        .action(queryStatus);
+    // Clear state
+    monitorCmd
+        .command('clear')
+        .description('Clear monitor state (reset)')
+        .action(clearState);
+}
+//# sourceMappingURL=cicd-monitor.js.map