specweave 0.32.2 → 0.32.3

package/plugins/specweave/skills/code-standards-analyzer/SKILL.md

@@ -408,9 +408,15 @@ Full standards: .specweave/docs/internal/governance/coding-standards.md"
 ### Supported Languages
 - ✅ TypeScript (primary)
 - ✅ JavaScript (ES6+)
-- 🔜 Python (future)
-- 🔜 Java (future)
-- 🔜 Go (future)
+- ✅ Python (pyproject.toml, .pylintrc, ruff.toml, .flake8, mypy.ini)
+- ✅ Java/Kotlin (checkstyle.xml, pmd.xml, spotbugs.xml, detekt.yml)
+- ✅ Go (go.mod, .golangci.yml, staticcheck.conf)
+- ✅ C#/.NET (.editorconfig, StyleCop.json, Directory.Build.props)
+- ✅ Rust (rustfmt.toml, clippy.toml, Cargo.toml)
+- ✅ React (package.json, ESLint plugin:react/*)
+- ✅ Angular (angular.json, ESLint @angular-eslint)
+- ✅ Vue (package.json, ESLint plugin:vue/*)
+- ✅ Svelte (package.json, svelte.config.js)
 
 ### Detection Algorithms
 
@@ -439,14 +445,60 @@ Full standards: .specweave/docs/internal/governance/coding-standards.md"
 
 1. **Implicit Standards**: Requires representative codebase sample
 2. **False Positives**: Anti-pattern detection may flag intentional code
-3. **Language Support**: Currently TypeScript/JavaScript only
-4. **Context**: Can't understand business rationale for patterns
+3. **Context**: Can't understand business rationale for patterns
+
+---
+
+## Multi-Technology Support
+
+**Status**: ✅ Implemented (increment 0122-multi-technology-governance)
+
+| Technology | Config Files | Status |
+|------------|--------------|--------|
+| TypeScript/JavaScript | `.eslintrc.*`, `.prettierrc`, `tsconfig.json` | ✅ Implemented |
+| Python | `pyproject.toml`, `.pylintrc`, `ruff.toml`, `.flake8`, `mypy.ini` | ✅ Implemented |
+| Go | `go.mod`, `.golangci.yml`, `staticcheck.conf` | ✅ Implemented |
+| Java/Kotlin | `checkstyle.xml`, `pmd.xml`, `spotbugs.xml`, `detekt.yml` | ✅ Implemented |
+| C#/.NET | `.editorconfig`, `StyleCop.json`, `Directory.Build.props` | ✅ Implemented |
+| Rust | `rustfmt.toml`, `clippy.toml`, `Cargo.toml` | ✅ Implemented |
+| React | ESLint + `plugin:react/*`, `package.json` | ✅ Implemented |
+| Angular | `angular.json`, `.eslintrc` | ✅ Implemented |
+| Vue | ESLint + `plugin:vue/*`, `vite.config.*` | ✅ Implemented |
+| Svelte | `svelte.config.js`, `package.json` | ✅ Implemented |
+
+**Output Structure:**
+```
+.specweave/docs/internal/governance/
+├── coding-standards.md          # Unified summary of ALL technologies
+├── shared-conventions.md        # EditorConfig, Git conventions
+└── standards/
+    ├── typescript.md
+    ├── python.md
+    ├── golang.md
+    ├── java.md
+    ├── react.md
+    ├── angular.md
+    ├── vue.md
+    └── svelte.md
+```
+
+**Usage**:
+```typescript
+import {
+  detectEcosystems,
+  parsePythonStandards,
+  parseGoStandards,
+  parseJavaStandards,
+  parseFrontendStandards,
+  generateStandardsMarkdown,
+  generateUnifiedSummary
+} from 'src/core/living-docs/governance/index.js';
+```
 
 ---
 
 ## Future Enhancements
 
-- [ ] Multi-language support (Python, Java, Go)
 - [ ] Auto-generate ESLint rules from detected patterns
 - [ ] AI-powered suggestions from top OSS projects
 - [ ] Team-specific standards in multi-project mode

package/plugins/specweave/skills/increment-planner/SKILL.md

@@ -176,39 +176,68 @@ echo "Using coverageTarget: $coverageTarget"
 
 **Store these values for use in STEP 4 and STEP 7!**
 
-### STEP 0B: Detect Structure Level & Select Project/Board (MANDATORY!)
+### STEP 0B: Get Project Context (MANDATORY - BLOCKING!)
 
-**⚠️ CRITICAL: Before generating spec.md, you MUST know the target project (and board for 2-level structures)!**
+**⛔ DO NOT PROCEED TO STEP 1 WITHOUT COMPLETING THIS STEP!**
 
-**Structure Levels:**
-- **1-Level**: `internal/specs/{project}/FS-XXX/` - requires `project` in spec.md
-- **2-Level**: `internal/specs/{project}/{board}/FS-XXX/` - requires BOTH `project` AND `board`
+Before generating ANY spec.md content, you MUST run this CLI command:
 
-**Detection Logic** (use `src/utils/structure-level-detector.ts`):
+```bash
+specweave context projects
+```
 
-```typescript
-import { detectStructureLevel, getRequiredSpecFields } from './utils/structure-level-detector.js';
+This returns JSON with available projects and structure level:
 
-const structureConfig = detectStructureLevel(projectRoot);
-console.log(`Structure level: ${structureConfig.level}`);
-console.log(`Detection reason: ${structureConfig.detectionReason}`);
-console.log(`Available projects: ${structureConfig.projects.map(p => p.id).join(', ')}`);
+```json
+{
+  "level": 1,
+  "projects": [{"id": "my-app", "name": "My App"}],
+  "detectionReason": "multiProject configuration",
+  "source": "multi-project"
+}
+```
 
-if (structureConfig.level === 2 && structureConfig.boardsByProject) {
-  console.log('Available boards by project:');
-  for (const [projectId, boards] of Object.entries(structureConfig.boardsByProject)) {
-    console.log(`  ${projectId}: ${boards.map(b => b.id).join(', ')}`);
-  }
+**For 2-level structures**, output includes boards:
+```json
+{
+  "level": 2,
+  "projects": [{"id": "acme-corp", "name": "ACME Corporation"}],
+  "boardsByProject": {
+    "acme-corp": [
+      {"id": "digital-ops", "name": "Digital Operations"},
+      {"id": "mobile-team", "name": "Mobile Team"}
+    ]
+  },
+  "detectionReason": "ADO area path mapping configured",
+  "source": "ado-area-path"
 }
 ```
 
-**Manual Detection:**
+**VALIDATION RULES:**
+
+```
+✅ REQUIRED: Parse the JSON output and use ONLY those project/board values
+✅ REQUIRED: project field MUST match one of the returned projects[].id
+✅ REQUIRED: board field (2-level) MUST match one of boardsByProject[project].id
+❌ FORBIDDEN: Inventing or guessing project names
+❌ FORBIDDEN: Using folder name as project (e.g., "sw-olysense")
+❌ FORBIDDEN: Creating spec.md with {{PROJECT_ID}} placeholder
+❌ FORBIDDEN: Creating spec.md for 2-level without board: field
+```
+
+**Structure Levels:**
+- **1-Level**: `internal/specs/{project}/FS-XXX/` - requires `project` in spec.md
+- **2-Level**: `internal/specs/{project}/{board}/FS-XXX/` - requires BOTH `project` AND `board`
+
+**Alternative: Interactive Selection:**
 ```bash
-# Check if 2-level (ADO area paths or JIRA boards)
-jq '.sync.profiles | to_entries[] | select(.value.provider == "ado") | .value.config.areaPathMapping' .specweave/config.json
+specweave context select
+# Returns auto-selected or prompts for selection
+```
 
-# Check existing folder structure
-ls -la .specweave/docs/internal/specs/*/  # If sub-folders exist (not FS-XXX) → 2-level
+**Get boards for a specific project (2-level):**
+```bash
+specweave context boards --project=acme-corp
 ```
 
 **Project/Board Selection - ULTRA-SMART LOGIC (MANDATORY BEFORE STEP 4!):**
@@ -766,19 +795,21 @@ When creating tasks, assign optimal models:
 - Simple CRUD, configuration, setup
 - Mechanical work with defined approach
 
-**🧠 Sonnet** (thinking, balanced):
+**💎 Opus** (best quality, default):
 - Architecture decisions
 - Multiple valid approaches
 - Integration between components
 - Complex business logic
 - Error handling strategies
-
-**💎 Opus** (critical, expensive):
 - Critical system architecture
 - Security-critical decisions
 - Performance-critical algorithms
 - Novel problem-solving
 
+**🧠 Sonnet** (legacy, rarely needed):
+- Use only for backwards compatibility
+- Prefer Opus or Haiku instead
+
 ---
 
 ## Validation Checklist

package/plugins/specweave/skills/increment-planner/templates/spec-multi-project.md

@@ -8,8 +8,10 @@ created: {{DATE}}
 structure: user-stories
 test_mode: {{TEST_MODE}}
 coverage_target: {{COVERAGE_TARGET}}
-default_project: {{PROJECT_ID}}
-default_board: {{BOARD_ID}}
+# MANDATORY: Run "specweave context projects" to get valid project/board IDs
+# For 2-level structures: BOTH project AND board are REQUIRED
+project: {{PROJECT_ID}}
+board: {{BOARD_ID}}
 multi_project: true
 projects:
   - id: {{PROJECT_FE_ID}}

package/plugins/specweave/skills/increment-planner/templates/spec-single-project.md

@@ -8,7 +8,8 @@ created: {{DATE}}
 structure: user-stories
 test_mode: {{TEST_MODE}}
 coverage_target: {{COVERAGE_TARGET}}
-default_project: {{PROJECT_ID}}
+# MANDATORY: Run "specweave context projects" to get valid project ID
+project: {{PROJECT_ID}}
 ---
 
 # Feature: {{FEATURE_TITLE}}

package/plugins/specweave/skills/increment-planner/templates/tasks-multi-project.md

@@ -6,7 +6,7 @@
 - `[P]`: Parallelizable
 - `[ ]`: Not started
 - `[x]`: Completed
-- Model hints: ⚡ haiku, 🧠 sonnet, 💎 opus
+- Model hints: ⚡ haiku (simple), 💎 opus (default)
 
 ## Phase 1: Foundation & Setup
 

package/plugins/specweave/skills/increment-planner/templates/tasks-single-project.md

@@ -6,7 +6,7 @@
 - `[P]`: Parallelizable
 - `[ ]`: Not started
 - `[x]`: Completed
-- Model hints: ⚡ haiku, 🧠 sonnet, 💎 opus
+- Model hints: ⚡ haiku (simple), 💎 opus (default)
 
 ## Phase 1: Setup
 

package/plugins/specweave-ado/commands/cleanup-duplicates.md

@@ -0,0 +1,212 @@
+---
+name: specweave-ado:cleanup-duplicates
+description: Clean up duplicate Azure DevOps work items for a Feature. Finds work items with duplicate titles and closes all except the first created item.
+justification: |
+  CRITICAL INCIDENT RESPONSE TOOL - DO NOT DELETE!
+
+  Why This Command Exists:
+  - Prevention systems work for single-process execution
+  - Multiple parallel Claude Code instances bypass all prevention (file-based cache, no distributed locking)
+  - ADO API race conditions: Time gap between "check exists" and "create work item" allows duplicates
+  - Historical duplicates from pre-v0.33.0 users (before prevention was added)
+
+  Evidence of Need:
+  - GitHub had 123 duplicate issues incident (cleaned to 29 unique) - same risk exists for ADO
+  - Parallel execution creates race conditions that prevention CANNOT solve
+  - Industry standard: Prevention + Detection + Cleanup (defense in depth)
+
+  When to Delete:
+  - ONLY if distributed locking implemented
+  - AND parallel execution tested (100+ concurrent syncs with zero duplicates)
+  - AND zero duplicates for 6+ months in production
+---
+
+# Clean Up Duplicate ADO Work Items
+
+**CRITICAL**: This command detects and closes duplicate ADO work items created by multiple syncs.
+
+## Usage
+
+```bash
+/specweave-ado:cleanup-duplicates <feature-id> [--dry-run]
+```
+
+## What It Does
+
+**Duplicate Detection & Cleanup**:
+
+1. **Find all work items** for the Feature (searches by Feature ID in title)
+2. **Group by title** (detect duplicates)
+3. **For each duplicate group**:
+   - Keep the **FIRST created** work item (lowest ID)
+   - Close all **LATER** work items with comment: "Duplicate of #XXX"
+4. **Update Feature README** with correct work item IDs
+
+## Examples
+
+### Dry Run (No Changes)
+
+```bash
+/specweave-ado:cleanup-duplicates FS-031 --dry-run
+```
+
+**Output**:
+```
+Scanning for duplicates in Feature FS-031...
+   Found 25 total work items
+   Detected 10 duplicate groups:
+
+   Group 1: "[FS-031] External Tool Status Synchronization"
+      - #1250 (KEEP) - Created 2025-11-10
+      - #1255 (CLOSE) - Created 2025-11-11 - DUPLICATE
+      - #1260 (CLOSE) - Created 2025-11-12 - DUPLICATE
+
+   Group 2: "[FS-031] Multi-Project ADO Sync"
+      - #1251 (KEEP) - Created 2025-11-10
+      - #1256 (CLOSE) - Created 2025-11-11 - DUPLICATE
+
+   ...
+
+Dry run complete!
+   Total work items: 25
+   Duplicate groups: 10
+   Work items to close: 15
+
+This was a DRY RUN - no changes made.
+   Run without --dry-run to actually close duplicates.
+```
+
+### Actual Cleanup
+
+```bash
+/specweave-ado:cleanup-duplicates FS-031
+```
+
+**Output**:
+```
+Scanning for duplicates in Feature FS-031...
+   Found 25 total work items
+   Detected 10 duplicate groups
+
+CONFIRM: Close 15 duplicate work items? [y/N]
+> y
+
+Closing duplicates...
+   Closed #1255 (duplicate of #1250)
+   Closed #1256 (duplicate of #1251)
+   Closed #1260 (duplicate of #1250)
+   ...
+
+Updating Feature README frontmatter...
+   Updated frontmatter with correct work item IDs
+
+Cleanup complete!
+   Closed: 15 duplicates
+   Kept: 10 original work items
+```
+
+## Arguments
+
+- `<feature-id>` - Feature ID (e.g., `FS-031` or just `031`)
+- `--dry-run` - Preview changes without actually closing work items (optional)
+
+## Safety Features
+
+- **Confirmation prompt**: Asks before closing work items (unless --dry-run)
+- **Dry run mode**: Preview changes safely
+- **Keeps oldest work item**: Preserves the first created item
+- **Adds closure comment**: Links to the original work item
+- **Updates metadata**: Fixes Feature README frontmatter
+
+## What Gets Closed
+
+**Closed work items**:
+- Duplicate titles (second, third, etc. occurrences)
+- Closed with comment: "Duplicate of #XXX"
+- Original work item kept open (or maintains its status)
+
+**Example comment on closed duplicate**:
+```markdown
+## Duplicate of #1250
+
+This work item was automatically closed by SpecWeave cleanup because it is a duplicate.
+
+The original work item (#1250) contains the same content and should be used for tracking instead.
+
+Auto-closed by SpecWeave Duplicate Cleanup
+```
+
+## Requirements
+
+1. **Azure DevOps PAT** configured (`AZURE_DEVOPS_PAT`)
+2. **Organization** configured (`AZURE_DEVOPS_ORG`)
+3. **Project** configured (`AZURE_DEVOPS_PROJECT`)
+4. **Write access** to project (for closing work items)
+5. **Feature folder exists** at `.specweave/docs/internal/specs/FS-XXX-name/`
+
+## When to Use
+
+**Use this command when**:
+- You see multiple work items with the same title in ADO
+- Feature sync ran multiple times and created duplicates
+- Feature README frontmatter got corrupted and reset
+- Post-sync validation warns about duplicates
+
+**Example warning that triggers this**:
+```
+WARNING: 10 duplicate(s) detected!
+   Run cleanup command to resolve:
+   /specweave-ado:cleanup-duplicates FS-031
+```
+
+## Architecture
+
+**Duplicate Detection Logic**:
+1. Query WIQL for work items with Feature ID in title
+2. Group work items by **exact title match**
+3. Within each group, sort by **work item ID** (ascending)
+4. Keep **first work item** (lowest ID = oldest)
+5. Close **all others** as duplicates via state transition
+
+**Why lowest ID?**:
+- Lower work item IDs were created first
+- Preserves chronological order
+- Maintains links from old documentation
+
+## Related Commands
+
+- `/specweave-ado:sync` - Sync Feature to ADO (with duplicate detection)
+- `/specweave-ado:reconcile` - Reconcile work item states
+- `/specweave:validate` - Validate increment completeness
+
+## Implementation
+
+**File**: `plugins/specweave-ado/lib/ado-duplicate-detector.ts`
+
+**Class**: `AdoDuplicateDetector`
+
+**Algorithm** (3-phase protection):
+1. **Detection**: WIQL query for existing work items matching pattern
+2. **Verification**: Count check to detect duplicates after creation
+3. **Reflection**: Auto-close duplicates automatically
+
+For manual cleanup:
+1. WIQL query for all work items with Feature ID
+2. Group by title (Map<string, number[]>)
+3. Filter groups with >1 item (duplicates)
+4. For each duplicate group:
+   - Keep first work item (lowest ID)
+   - Close others via ADO REST API
+
+## Next Steps
+
+After cleanup:
+
+1. **Verify cleanup**: Check ADO for remaining work items
+2. **Check Feature FEATURE.md**: Verify frontmatter has correct work item IDs
+3. **Re-run sync**: `/specweave-ado:sync` (should show no duplicates)
+4. **Duplicate detection**: Automatically enabled via AdoDuplicateDetector
+
+---
+
+**SAFE TO USE**: This command is idempotent and safe to run multiple times.

package/plugins/specweave-ado/commands/reconcile.md

@@ -0,0 +1,120 @@
+---
+name: specweave-ado:reconcile
+description: Reconcile Azure DevOps work item states with increment statuses. Fixes drift by closing work items for completed increments and reactivating work items for resumed increments.
+---
+
+# Azure DevOps Status Reconciliation
+
+Scan all increments and fix any drift between local metadata.json status and ADO work item states.
+
+## Usage
+
+```bash
+/specweave-ado:reconcile [options]
+```
+
+## Options
+
+- `--dry-run`: Preview changes without making them
+- `--verbose`: Show detailed output for each work item checked
+
+## What It Does
+
+1. **Scans** all non-archived increments
+2. **Compares** metadata.json status with ADO work item state
+3. **Fixes** mismatches:
+   - `metadata=completed` + `ADO=Active` → **Close** the work item
+   - `metadata=in-progress` + `ADO=Closed` → **Reactivate** the work item
+
+## When to Use
+
+- After manual metadata.json edits
+- After git pulls that changed increment statuses
+- When you notice active work items for completed work
+- As a periodic health check
+
+## Implementation
+
+Run the reconciliation using the AdoReconciler:
+
+```typescript
+import { AdoReconciler } from '../../../src/sync/ado-reconciler.js';
+
+const reconciler = new AdoReconciler({
+  projectRoot: process.cwd(),
+  dryRun: args.includes('--dry-run'),
+});
+
+const result = await reconciler.reconcile();
+
+// Report results
+console.log(`\nReconciliation complete:`);
+console.log(`  Scanned: ${result.scanned} increments`);
+console.log(`  Fixed: ${result.closed} closed, ${result.reopened} reopened`);
+if (result.errors.length > 0) {
+  console.log(`  Errors: ${result.errors.length}`);
+}
+```
+
+## Example Output
+
+```
+📊 Scanning 5 increment(s) for ADO state drift...
+
+  ✅ Work Item #1234 (0056-plugin-fix/US-001): State matches (Active)
+  ❌ Work Item #1240 (0066-import-wizard/US-003): Active but should be CLOSED (status=completed)
+     ✅ Closed work item #1240
+  ❌ Work Item #1238 (0063-multi-repo/US-001): CLOSED but should be ACTIVE (status=in-progress)
+     ✅ Reactivated work item #1238
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+📊 ADO RECONCILIATION SUMMARY
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+   Increments scanned:   5
+   Mismatches found:     2
+   Work items closed:    1
+   Work items reopened:  1
+   Errors:               0
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Dry Run Mode
+
+```bash
+/specweave-ado:reconcile --dry-run
+```
+
+Shows what would be changed without making any modifications:
+
+```
+  ❌ Work Item #1240 (0066-import-wizard/US-003): Active but should be CLOSED
+     [DRY RUN] Would close work item #1240
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+📊 ADO RECONCILIATION SUMMARY
+   ⚠️  DRY RUN - No changes were made
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Requirements
+
+- Azure DevOps PAT configured (`AZURE_DEVOPS_PAT`)
+- `sync.ado.enabled = true` in config.json
+- `sync.settings.canUpdateExternalItems = true` in config.json
+
+## ADO Status Mapping
+
+| SpecWeave Status | Expected ADO State |
+|-----------------|-------------------|
+| `completed` | Closed, Done, Resolved |
+| `abandoned` | Closed, Removed |
+| `in-progress` | Active, In Progress |
+| `active` | Active, New |
+| `planning` | New |
+
+## Related Commands
+
+- `/specweave-ado:status`: View sync status for increments
+- `/specweave-ado:sync`: Manual sync to ADO
+- `/specweave:done`: Close increment (triggers auto-close)
+- `/specweave:resume`: Resume increment (now triggers auto-reopen)