specweave 0.21.2 → 0.22.0

package/CLAUDE.md

@@ -24,21 +24,23 @@ Users receive a different CLAUDE.md via the template system.
 /SESSION-SUMMARY-2025-10-28.md         # NO! Goes to increment reports/
 /ADR-006-DEEP-ANALYSIS.md              # NO! Goes to .specweave/docs/internal/architecture/adr/
 /ANALYSIS-MULTI-TOOL-COMPARISON.md     # NO! Goes to increment reports/
+/QUICK-START.md                        # NO! Goes to increment reports/
 /migration-helper.sh                   # NO! Goes to increment scripts/
 /execution.log                         # NO! Goes to increment logs/
 
 ✅ CORRECT - INCREMENT FOLDERS:
 .specweave/increments/0004-plugin-architecture/
-├── spec.md                            # Spec files (core 3)
+├── spec.md                            # ⚠️ ONLY THESE 3 FILES in root!
 ├── plan.md
 ├── tasks.md                           # Tasks with embedded tests
-├── reports/                           # ✅ PUT REPORTS HERE!
+├── reports/                           # ✅ ALL REPORTS HERE!
 │   ├── PLUGIN-MIGRATION-COMPLETE.md   # ✅ Completion reports
 │   ├── SESSION-SUMMARY.md             # ✅ Session summaries
+│   ├── QUICK-START.md                 # ✅ Quick start guides
 │   └── ANALYSIS-*.md                  # ✅ Analysis files
-├── scripts/                           # ✅ PUT SCRIPTS HERE!
+├── scripts/                           # ✅ ALL SCRIPTS HERE!
 │   └── migration-helper.sh            # ✅ Helper scripts
-└── logs/                              # ✅ PUT LOGS HERE!
+└── logs/                              # ✅ ALL LOGS HERE!
     └── execution.log                  # ✅ Execution logs
 
 .specweave/docs/internal/architecture/ # ✅ PUT ADRS/DIAGRAMS HERE!
@@ -48,6 +50,105 @@ Users receive a different CLAUDE.md via the template system.
 
 **Before committing, ALWAYS check**: `git status` - If you see `.md` files in root, MOVE THEM!
 
+### 📁 Increment Structure Rules (MANDATORY)
+
+**ONLY 3 files allowed in increment root**:
+1. ✅ `spec.md` - Specification
+2. ✅ `plan.md` - Implementation plan
+3. ✅ `tasks.md` - Tasks with embedded tests
+
+**Everything else MUST be in subfolders**:
+- `reports/` - Session summaries, completion reports, analysis files, quick-start guides
+- `scripts/` - Helper scripts, migrations, utilities
+- `logs/` - Execution logs, debug output, temp files
+
+**Examples of files that belong in subfolders**:
+- `QUICK-START.md` → `reports/QUICK-START.md`
+- `SESSION-NOTES.md` → `reports/SESSION-NOTES.md`
+- `ULTRATHINK-*.md` → `reports/ULTRATHINK-*.md`
+- `validation.sh` → `scripts/validation.sh`
+- `debug.log` → `logs/debug.log`
+
+**Why this matters**:
+- ✅ Clean, predictable structure
+- ✅ Easy to find files by type
+- ✅ No increment root clutter
+- ✅ Consistent across all increments
+
+---
+
+## 🛡️ CRITICAL: NEVER DELETE .specweave/ DIRECTORIES!
+
+**⛔ MASS DELETION PROTECTION IS ACTIVE ⛔**
+
+**PROTECTED DIRECTORIES**:
+- `.specweave/docs/` - All project documentation (internal + public)
+- `.specweave/increments/` - All increment history and specifications
+
+**WHAT THIS MEANS**:
+- ❌ **NEVER** run `rm -rf .specweave/docs` or `rm -rf .specweave/increments`
+- ❌ **NEVER** delete more than 50 files in these directories at once
+- ✅ Pre-commit hook will **BLOCK** accidental mass deletions
+- ✅ If intentional, bypass with `git commit --no-verify`
+
+**WHY THIS EXISTS**:
+On 2025-11-17, an accidental mass deletion occurred (1,200+ files). All files were recovered via `git restore`, but this protection prevents future incidents.
+
+**IF YOU ACCIDENTALLY DELETE**:
+```bash
+# Immediately restore:
+git restore .specweave/
+
+# Verify restoration:
+git status
+```
+
+**See**: `.specweave/increments/0039/reports/ACCIDENTAL-DELETION-RECOVERY-2025-11-17.md`
+
+---
+
+## ⚠️ CRITICAL: NEVER USE `specweave init . --force` FOR REINSTALLS!
+
+**⛔ COMMON MISTAKE THAT DELETES ALL DATA ⛔**
+
+**THE DANGER**:
+```bash
+# ❌ DANGEROUS (deletes ALL increments and docs):
+specweave init . --force
+
+# What --force actually does:
+# 1. Skips all confirmation prompts
+# 2. AUTOMATICALLY DELETES .specweave/ entirely
+# 3. Loses all increments, docs, and history
+# 4. No backup unless you create one manually
+```
+
+**SAFE ALTERNATIVES**:
+```bash
+# ✅ SAFE - Update files, keep all data:
+specweave init .
+# When prompted, select: "Continue working"
+
+# ✅ SAFE - Always interactive, never deletes:
+npx specweave init .
+```
+
+**WHY THIS MATTERS**:
+- Documentation used to recommend `--force` for troubleshooting (FIXED in v0.21.4+)
+- Users followed the docs and lost all their work
+- Now `--force` has multiple safeguards:
+  - ⚠️ BIG RED WARNING before deletion
+  - ✅ ALWAYS requires confirmation (even in force mode)
+  - 📦 Automatic backup created before deletion
+  - 🔒 Pre-commit hook blocks accidental commits
+
+**IF YOU NEED A FRESH START**:
+1. Backup first: `cp -r .specweave .specweave.backup-$(date +%Y%m%d)`
+2. Run: `specweave init .` (select "Fresh start" option)
+3. Or: `specweave init . --force` (requires confirmation + creates auto-backup)
+
+**NEVER use `--force` unless you want to DELETE EVERYTHING!**
+
 ---
 
 ## Tool Support
@@ -340,20 +441,338 @@ GitHub Issue (Checkable task list for stakeholders)
 
 ## Build & Test
 
+### Build Commands
+
 ```bash
-# Build
-npm run build
+# ALWAYS use clean build during development (prevents TS5055 errors)
+npm run rebuild             # Clean + build (RECOMMENDED)
 
-# Test
-npm test                    # Unit tests
+# Or manual steps:
+npm run clean              # Remove dist/ folder
+npm run build              # Compile TypeScript
+```
+
+### Testing
+
+**Test Framework**: **Vitest** (migrated from Jest on 2025-11-17)
+
+```bash
+npm test                    # Smoke tests (quick validation)
+npm run test:unit           # Unit tests with Vitest
+npm run test:integration    # Integration tests with Vitest
 npm run test:e2e            # E2E tests (Playwright)
-npm run test:integration    # Integration tests
+npm run test:all            # All tests
+npm run test:coverage       # Coverage report
+```
+
+**Why Vitest?**
+- ✅ ESM-native (no tsconfig hacks)
+- ✅ Faster than Jest
+- ✅ Better TypeScript integration
+- ✅ Native import.meta.url support
+- ✅ Modern, actively maintained
+
+**Test Organization** (4 categories):
+- `tests/unit/` - Pure logic tests (no I/O) - **Vitest**
+- `tests/plugin-validation/` - Plugin structure contracts
+- `tests/integration/` - 4 semantic categories - **Vitest**:
+  - `external-tools/` - GitHub, JIRA, ADO, Kafka sync
+  - `core/` - Core framework + workflows
+  - `generators/` - Code generation (frontend, backend, ML)
+  - `features/` - Feature plugins (Figma, i18n, diagrams, etc.)
+- `tests/e2e/` - Full user scenarios - **Playwright**
+
+**Writing Tests**:
+```typescript
+// Import from vitest (NOT jest)
+import { describe, it, expect, beforeEach, vi } from 'vitest';
+
+// Mocking
+vi.mock('fs/promises');
+const mockFn = vi.fn();
+vi.clearAllMocks();
+```
+
+**Details**: `.specweave/docs/internal/architecture/TEST-ORGANIZATION-PROPOSAL.md`
+
+### Test Isolation (CRITICAL - Prevents .specweave/ Deletion!)
+
+**🚨 MANDATORY FOR ALL TESTS creating .specweave/ structures:**
+
+**THE PROBLEM**: Tests using `process.cwd()` can accidentally delete the project `.specweave/` folder containing all your work!
+
+**CORRECT PATTERN** (ALWAYS use this):
+```typescript
+import * as os from 'os';
+import * as path from 'path';
+
+// ✅ SAFE: Uses isolated temp directory
+const testRoot = path.join(os.tmpdir(), 'test-name-' + Date.now());
+```
+
+**DANGEROUS PATTERN** (NEVER use this):
+```typescript
+// ❌ DANGER: Creates directories in project root!
+const testRoot = path.join(process.cwd(), '.test-something');
+const testPath = path.join(__dirname, '..', '.specweave', 'increments');
+```
+
+**Why This Matters**:
+1. Tests create mock `.specweave/` structures for testing
+2. Cleanup uses `fs.rm(testRoot, { recursive: true })`
+3. If `testRoot` points to project root → **DELETES REAL .specweave/!**
+4. You lose all increments, docs, and history
+
+**Use Test Utilities** (RECOMMENDED):
+```typescript
+import { createIsolatedTestDir, createSpecweaveStructure } from '../test-utils/isolated-test-dir';
+
+test('my test', async () => {
+  const { testDir, cleanup } = await createIsolatedTestDir('my-test');
+
+  try {
+    // Setup .specweave structure in isolated directory
+    await createSpecweaveStructure(testDir);
+
+    // Test code here - NEVER touches project .specweave/
+    const incrementPath = path.join(testDir, '.specweave', 'increments', '0001-test');
+    // ...
+  } finally {
+    await cleanup(); // ALWAYS cleanup
+  }
+});
 ```
 
-**Coverage Requirements**:
+**Protection Layers**:
+1. ✅ **Pre-commit hook**: Blocks commits with dangerous test patterns
+2. ✅ **Test utilities**: `tests/test-utils/isolated-test-dir.ts`
+3. ✅ **Documentation**: This section
+
+**Related Incident**: 2025-11-17 - Multiple `.specweave/` deletions traced to dangerous test patterns
+**Root Cause Analysis**: `.specweave/increments/0037/reports/DELETION-ROOT-CAUSE-2025-11-17.md`
+
+### Build Health Checks
+
+**CRITICAL**: TypeScript ES Modules require specific practices:
+
+1. **Always Import with .js Extensions**:
+   ```typescript
+   // ❌ WRONG (will break at runtime):
+   import { foo } from './bar';
+
+   // ✅ CORRECT:
+   import { foo } from './bar.js';
+   ```
+
+2. **Fix Missing Extensions**:
+   ```bash
+   # Auto-fix all missing .js extensions:
+   node scripts/fix-js-extensions.js
+
+   # Preview changes first:
+   node scripts/fix-js-extensions.js --dry-run
+   ```
+
+3. **Verify Build is Clean**:
+   ```bash
+   # Check for polluted dist/ (TS5055 indicator):
+   find dist/src -name "*.ts" -not -name "*.d.ts"
+   # Should return NOTHING
+
+   # If files found, clean rebuild:
+   npm run rebuild
+   ```
+
+4. **Test Hook Execution**:
+   ```bash
+   # Hooks must import correctly at runtime:
+   node plugins/specweave/lib/hooks/update-ac-status.js 0001
+   # Should execute without "Cannot find module" errors
+   ```
+
+5. **Install Git Hooks** (RECOMMENDED):
+   ```bash
+   bash scripts/install-git-hooks.sh
+   # Verifies build health before every commit
+   ```
+
+### Common Build Errors & Fixes
+
+**Error: TS5055 - Cannot write file (would overwrite input)**
+```bash
+# Cause: dist/ polluted with .ts source files
+# Fix:
+npm run clean && npm run build
+```
+
+**Error: Cannot find module 'src/...' (hook execution)**
+```bash
+# Cause: Hooks importing from src/ instead of dist/src/
+#    OR: Missing .js extensions in imports
+# Fix:
+node scripts/fix-js-extensions.js
+npm run rebuild
+```
+
+**Error: Module import without .js extension**
+```bash
+# Cause: TypeScript ES modules REQUIRE .js in relative imports
+# Fix:
+node scripts/fix-js-extensions.js
+```
+
+### Build Architecture
+
+SpecWeave uses **dual compilation**:
+- `tsc`: Compiles `src/` → `dist/src/` (source files)
+- `esbuild`: Compiles `plugins/**/lib/hooks/*.ts` → in-place `.js` (hooks only)
+
+**Why?** Hooks must import from `dist/src/` (compiled), but TypeScript would try to compile them before `dist/` exists (chicken-and-egg). Solution: Exclude hooks from `tsconfig.json`, compile separately with esbuild.
+
+### Increment Scripts vs Hooks
+
+**CRITICAL DISTINCTION**: Increment scripts and hooks have different purposes and import patterns.
+
+**Hooks** (`plugins/**/lib/hooks/*.ts`):
+- **Purpose**: Production runtime executables (called by shell scripts)
+- **Execution**: `#!/usr/bin/env node` (JavaScript runtime)
+- **Imports**: MUST use `dist/src/` (compiled JavaScript)
+- **Compilation**: esbuild (separate from main build)
+- **Example**:
+  ```typescript
+  #!/usr/bin/env node
+  import { ACStatusManager } from '../../../../dist/src/core/increment/ac-status-manager.js';
+  ```
+
+**Increment Scripts** (`.specweave/increments/####/scripts/*.ts`):
+- **Purpose**: Development utilities (one-off tasks, migrations, analysis)
+- **Execution**: `#!/usr/bin/env tsx` (TypeScript runtime with ESM support)
+- **Imports**: MUST use `src/` (TypeScript source, NOT compiled)
+- **Compilation**: None (tsx transpiles on-the-fly)
+- **Example**:
+  ```typescript
+  #!/usr/bin/env tsx
+  import { ACStatusManager } from '../../../../src/core/increment/ac-status-manager.js';
+  ```
+
+**Why Different Patterns?**
+
+| Aspect | Hooks (dist/) | Increment Scripts (src/) |
+|--------|---------------|-------------------------|
+| **Context** | Production runtime | Development only |
+| **Tooling** | Node.js only | TypeScript tooling (tsx) |
+| **Build dependency** | Yes (requires dist/) | No (live source code) |
+| **Live reload** | No (must rebuild) | Yes (tsx auto-transpiles) |
+| **Purpose** | Permanent infrastructure | Temporary dev utilities |
+
+**Common Mistake**: Copying hook import patterns to increment scripts.
+
+```typescript
+// ❌ WRONG (increment script importing from dist/):
+#!/usr/bin/env tsx
+import { ACStatusManager } from '../../../../dist/src/core/...';
+// Issues:
+// - Requires npm run build before execution
+// - Stale code if src/ changes without rebuild
+// - Semantic confusion (TS runtime + JS imports)
+
+// ✅ CORRECT (increment script importing from src/):
+#!/usr/bin/env tsx
+import { ACStatusManager } from '../../../../src/core/...';
+// Benefits:
+// - No build dependency
+// - Always uses latest source code
+// - Clear dev script pattern
+```
+
+**Note**: Use `tsx` (not `ts-node`) for increment scripts - it has better ESM + TypeScript support.
+
+### Running Increment Scripts
+
+**CRITICAL**: Increment scripts use `#!/usr/bin/env tsx` shebang, which assumes tsx is in your PATH. This often fails in development environments.
+
+**Recommended Execution Method** (Always Works):
+```bash
+# ✅ Use npx - finds tsx in node_modules/.bin/ automatically
+npx tsx .specweave/increments/####/scripts/script-name.ts
+
+# Example:
+npx tsx .specweave/increments/0037-project-specific-tasks/scripts/validate-task-consistency.ts
+```
+
+**Why npx?**
+- ✅ Works without global tsx installation
+- ✅ Uses project's tsx version (consistent across team)
+- ✅ No PATH configuration needed
+- ✅ Same behavior in CI/CD and local dev
+
+**Alternative Methods** (Less Recommended):
+```bash
+# Option 1: Direct execution (requires global tsx)
+chmod +x script.ts
+./script.ts
+# ❌ Fails if tsx not globally installed
+
+# Option 2: Install tsx globally (not recommended for teams)
+npm install -g tsx
+./script.ts
+# ❌ Every contributor must install globally
+# ❌ Version inconsistencies across team
+
+# Option 3: Full path
+./node_modules/.bin/tsx script.ts
+# ✅ Works, but verbose
+```
+
+**Troubleshooting "command not found: tsx" (Exit Code 127)**:
+
+This error means tsx isn't in your shell's PATH.
+
+**Root Cause**:
+- tsx is a **dev dependency** (installed in `node_modules/`)
+- Shell can't find commands in `node_modules/.bin/` automatically
+- npm scripts add `node_modules/.bin/` to PATH, but direct shell execution doesn't
+
+**Fix**:
+```bash
+# Instead of:
+tsx script.ts          # ❌ Fails with error 127
+
+# Use:
+npx tsx script.ts      # ✅ Always works
+```
+
+**Why This Happens "Sometimes"**:
+- **npm scripts**: Work (PATH includes node_modules/.bin/)
+- **Direct shell**: Fails (PATH doesn't include node_modules/.bin/)
+- **Global tsx installed**: Works (tsx in system PATH)
+- **CI/CD**: Depends on environment setup
+
+**Execution Context Comparison**:
+
+| Method | tsx in PATH? | Works? |
+|--------|--------------|--------|
+| `npm run script` | ✅ Yes (npm adds it) | ✅ Yes |
+| `./script.ts` | ❌ No (unless global) | ❌ Usually fails |
+| `tsx script.ts` | ❌ No (unless global) | ❌ Usually fails |
+| `npx tsx script.ts` | ✅ Yes (npx finds it) | ✅ Always works |
+
+**Best Practice for Contributors**:
+- **Creating scripts**: Use `#!/usr/bin/env tsx` shebang (conventional)
+- **Running scripts**: Always use `npx tsx script.ts` (reliable)
+- **Documentation**: Show npx execution method in examples
+
+### Coverage Requirements
+
 - Critical paths: 90%+
 - Overall: 80%+
 
+### Related Documentation
+
+- Build process details: `.github/CONTRIBUTING.md` → "Build Process & Best Practices"
+- Ultrathink analysis: `.specweave/increments/0039/reports/HOOK-IMPORT-ERROR-ULTRATHINK-ANALYSIS.md`
+- Build verification tests: `tests/integration/build/build-verification.test.ts`
+
 ---
 
 ## Common Tasks

package/README.md

@@ -232,8 +232,18 @@ Claude implements Task 1:
 # Install SpecWeave
 npm install -g specweave
 
-# Initialize new project
+# Initialize with Strategic Init (AI-powered research)
 specweave init my-project
+
+# Strategic Init guides you through 6 phases:
+# Phase 1: Vision & Market Research
+# Phase 2: Scaling & Performance Goals
+# Phase 3: Data & Compliance Detection
+# Phase 4: Budget & Cloud Credits
+# Phase 5: Methodology & Organization
+# Phase 6: Repository Selection (optional)
+
+# Result: Architecture recommendation, team plan, cost estimates
 cd my-project
 
 # Start building
@@ -242,6 +252,15 @@ cd my-project
 /specweave:done 0001                        # Complete increment
 ```
 
+### Multi-Project Setup
+```bash
+# Initialize with multiple projects
+specweave init --projects backend,frontend,mobile
+
+# Tasks automatically split by project keyword detection
+# Each project gets its own user stories and GitHub issues
+```
+
 ### Brownfield (Existing Project)
 ```bash
 # Initialize SpecWeave in existing project
@@ -255,7 +274,7 @@ specweave init .
 /specweave:increment "Add dark mode"
 ```
 
-**[→ Complete Quickstart Guide](https://spec-weave.com/docs/guides/getting-started/quickstart)**
+**[→ Complete Quickstart Guide](https://spec-weave.com/docs/guides/getting-started/quickstart)** | **[→ Strategic Init Guide](https://spec-weave.com/docs/guides/strategic-init)**
 
 ---
 
@@ -296,12 +315,23 @@ specweave init .
 
 ## Key Features
 
+### Strategic Init - AI-Powered Architecture Planning (NEW!)
+
+- 🎯 **Research-Driven Discovery** - Answer 6 phases of questions about your product
+- 🏗️ **Architecture Recommendations** - Tech stack, scaling strategy, cost projections
+- 🔒 **Compliance Detection** - Auto-detects 30+ standards (HIPAA, GDPR, SOC2, etc.)
+- 👥 **Smart Team Planning** - Current and future team structure, hiring roadmap
+- ☁️ **Cloud Credits Discovery** - AWS Activate, Azure Startup, GCP eligibility
+- 📦 **Repository Selection** - Batch select 1-100+ repos with intelligent routing
+
+### Production Features
+
 - 🤖 **AI-Native Enterprise Sync** - Claude updates JIRA/GitHub/ADO automatically (bidirectional!)
 - 📚 **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
-- 🔄 **Smart Reopen (NEW!)** - Report "broken" → Auto-detects what to reopen, respects WIP limits
+- 🔄 **Smart Reopen** - Report "broken" → Auto-detects what to reopen, respects WIP limits
 - 👥 **Multi-Project Tracking** - Unlimited JIRA/ADO/GitHub repos, intelligent routing
 - 🤖 **AI Agents** - PM, Architect, Quality Judge guide your work
 - 🔧 **CI/CD Auto-Fix** - Workflow failures auto-fixed by Claude (just mention `@claude`)

package/dist/plugins/specweave-github/lib/CodeValidator.d.ts

@@ -0,0 +1,101 @@
+/**
+ * Code Validator
+ *
+ * Validates that completed tasks have actual code implementation.
+ * Prevents marking tasks as complete when:
+ * - Files don't exist
+ * - Files are empty or have trivial content
+ * - Implementation is incomplete
+ *
+ * Used by ThreeLayerSyncManager to enforce code-completion discipline.
+ *
+ * @module CodeValidator
+ */
+/**
+ * File validation result
+ */
+export interface FileValidationResult {
+    path: string;
+    exists: boolean;
+    hasContent: boolean;
+    lineCount: number;
+    reason?: string;
+}
+/**
+ * Task validation result
+ */
+export interface TaskValidationResult {
+    taskId: string;
+    valid: boolean;
+    files: FileValidationResult[];
+    reason?: string;
+}
+/**
+ * CodeValidator options
+ */
+export interface CodeValidatorOptions {
+    minLines?: number;
+    minChars?: number;
+    projectRoot?: string;
+}
+export declare class CodeValidator {
+    private options;
+    constructor(options?: CodeValidatorOptions);
+    /**
+     * Validate that code exists for a task
+     *
+     * Extracts file paths from task description and verifies:
+     * 1. Files exist
+     * 2. Files have meaningful content
+     * 3. Files are not just stubs
+     *
+     * @param taskDescription - Task description with file paths
+     * @param taskId - Task ID for error messages
+     * @returns Validation result
+     */
+    validateTask(taskDescription: string, taskId: string): Promise<TaskValidationResult>;
+    /**
+     * Validate a single file
+     *
+     * @param filePath - Path to file (relative or absolute)
+     * @returns File validation result
+     */
+    validateFile(filePath: string): Promise<FileValidationResult>;
+    /**
+     * Extract file paths from task description
+     *
+     * Supports multiple formats:
+     * - **Files**: src/foo.ts, src/bar.ts
+     * - **Files to create**: src/foo.ts
+     * - **Files to modify**: src/bar.ts
+     * - Inline code blocks with file paths
+     *
+     * @param description - Task description text
+     * @returns Array of file paths
+     */
+    extractFilePaths(description: string): string[];
+    /**
+     * Batch validate multiple tasks
+     *
+     * @param tasks - Array of {taskId, description}
+     * @returns Array of validation results
+     */
+    validateTasks(tasks: Array<{
+        taskId: string;
+        description: string;
+    }>): Promise<TaskValidationResult[]>;
+    /**
+     * Get summary of validation results
+     *
+     * @param results - Array of task validation results
+     * @returns Summary statistics
+     */
+    summarizeResults(results: TaskValidationResult[]): {
+        total: number;
+        valid: number;
+        invalid: number;
+        noFiles: number;
+        invalidTasks: string[];
+    };
+}
+//# sourceMappingURL=CodeValidator.d.ts.map

package/dist/plugins/specweave-github/lib/CodeValidator.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"CodeValidator.d.ts","sourceRoot":"","sources":["../../../../plugins/specweave-github/lib/CodeValidator.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAKH;;GAEG;AACH,MAAM,WAAW,oBAAoB;IACnC,IAAI,EAAE,MAAM,CAAC;IACb,MAAM,EAAE,OAAO,CAAC;IAChB,UAAU,EAAE,OAAO,CAAC;IACpB,SAAS,EAAE,MAAM,CAAC;IAClB,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAED;;GAEG;AACH,MAAM,WAAW,oBAAoB;IACnC,MAAM,EAAE,MAAM,CAAC;IACf,KAAK,EAAE,OAAO,CAAC;IACf,KAAK,EAAE,oBAAoB,EAAE,CAAC;IAC9B,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAED;;GAEG;AACH,MAAM,WAAW,oBAAoB;IACnC,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,WAAW,CAAC,EAAE,MAAM,CAAC;CACtB;AAED,qBAAa,aAAa;IACxB,OAAO,CAAC,OAAO,CAAiC;gBAEpC,OAAO,GAAE,oBAAyB;IAQ9C;;;;;;;;;;;OAWG;IACG,YAAY,CAAC,eAAe,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC,oBAAoB,CAAC;IAsC1F;;;;;OAKG;IACG,YAAY,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAAC,oBAAoB,CAAC;IA4EnE;;;;;;;;;;;OAWG;IACH,gBAAgB,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,EAAE;IAuC/C;;;;;OAKG;IACG,aAAa,CAAC,KAAK,EAAE,KAAK,CAAC;QAAE,MAAM,EAAE,MAAM,CAAC;QAAC,WAAW,EAAE,MAAM,CAAA;KAAE,CAAC,GAAG,OAAO,CAAC,oBAAoB,EAAE,CAAC;IAS3G;;;;;OAKG;IACH,gBAAgB,CAAC,OAAO,EAAE,oBAAoB,EAAE,GAAG;QACjD,KAAK,EAAE,MAAM,CAAC;QACd,KAAK,EAAE,MAAM,CAAC;QACd,OAAO,EAAE,MAAM,CAAC;QAChB,OAAO,EAAE,MAAM,CAAC;QAChB,YAAY,EAAE,MAAM,EAAE,CAAC;KACxB;CAeF"}