specweave 0.28.9 → 0.28.13

package/plugins/specweave/skills/spec-generator/SKILL.md

@@ -46,6 +46,12 @@ description: Generates comprehensive specifications (spec.md, plan.md, tasks.md
 ### Target Audience
 
 ## User Stories & Acceptance Criteria
+
+<!--
+⚠️ MULTI-PROJECT MODE: If umbrella.enabled=true in config.json,
+   user stories MUST be project-scoped! See section below.
+-->
+
 ### US-001: [Title]
 **As a** [user type]
 **I want** [goal]
@@ -348,15 +354,172 @@ spec_generator:
 
 ---
 
+## 🔀 Multi-Project User Story Generation (v0.29.0+)
+
+**CRITICAL**: When umbrella/multi-project mode is detected, user stories MUST be generated per-project!
+
+### Detection (MANDATORY FIRST STEP)
+
+**Before generating spec.md, ALWAYS check for multi-project mode:**
+
+```bash
+# 1. Check config.json for umbrella mode
+cat .specweave/config.json | jq '.umbrella.enabled'
+
+# 2. Check for childRepos configuration
+cat .specweave/config.json | jq '.umbrella.childRepos[]'
+
+# 3. Check for project folders in specs/
+ls -la .specweave/docs/internal/specs/
+```
+
+**If ANY of these conditions are TRUE → Multi-project mode ACTIVE:**
+- `umbrella.enabled: true` in config.json
+- `umbrella.childRepos` has entries
+- Multiple project folders exist in `specs/` (e.g., `sw-app-fe/`, `sw-app-be/`, `sw-app-shared/`)
+- User prompt mentions: "3 repos", "frontend repo", "backend API", "shared library"
+
+### Project-Scoped User Story Format (MANDATORY in Multi-Project Mode)
+
+**❌ WRONG (Single-Project Format - DO NOT USE in multi-project!):**
+```markdown
+## User Stories
+
+### US-001: Thumbnail Upload
+As a content creator, I want to upload thumbnails...
+
+### US-002: CTR Prediction API
+As a system, I want to predict click-through rates...
+```
+
+**✅ CORRECT (Multi-Project Format - ALWAYS USE when umbrella detected!):**
+```markdown
+## User Stories by Project
+
+### Frontend (sw-thumbnail-ab-fe)
+
+#### US-FE-001: Thumbnail Upload & Comparison (P1)
+**Related Repo**: sw-thumbnail-ab-fe
+**As a** content creator
+**I want** to upload multiple thumbnail variants and compare them side-by-side
+**So that** I can visually evaluate my options before testing
+
+**Acceptance Criteria**:
+- [ ] **AC-FE-US1-01**: User can drag-and-drop up to 5 thumbnail images (JPG, PNG, WebP)
+- [ ] **AC-FE-US1-02**: Images are validated for YouTube specs (1280x720 min, <2MB)
+- [ ] **AC-FE-US1-03**: Side-by-side comparison view displays all variants
+
+---
+
+### Backend (sw-thumbnail-ab-be)
+
+#### US-BE-001: Thumbnail Analysis API (P1)
+**Related Repo**: sw-thumbnail-ab-be
+**As a** frontend application
+**I want** to call POST /predict-ctr endpoint
+**So that** I can get AI-powered click-through rate predictions
+
+**Acceptance Criteria**:
+- [ ] **AC-BE-US1-01**: POST /predict-ctr endpoint accepts thumbnail image
+- [ ] **AC-BE-US1-02**: ML model analyzes: face detection, text readability, color psychology
+
+---
+
+### Shared Library (sw-thumbnail-ab-shared)
+
+#### US-SHARED-001: Common Types & Validators (P1)
+**Related Repo**: sw-thumbnail-ab-shared
+**As a** developer in FE or BE repos
+**I want** shared TypeScript types and validators
+**So that** API contracts are consistent across projects
+
+**Acceptance Criteria**:
+- [ ] **AC-SHARED-US1-01**: ThumbnailMetadata type exported
+- [ ] **AC-SHARED-US1-02**: Validation schemas for image specs
+```
+
+### Project Classification Rules
+
+When analyzing user descriptions, classify each user story by keywords:
+
+| Keywords | Project | Prefix |
+|----------|---------|--------|
+| UI, component, page, form, view, drag-drop, theme, builder, menu display | Frontend | FE |
+| API, endpoint, CRUD, webhook, analytics, database, service, ML model | Backend | BE |
+| types, schemas, validators, utilities, localization, common | Shared | SHARED |
+| iOS, Android, mobile app, push notification | Mobile | MOBILE |
+| Terraform, K8s, Docker, CI/CD, deployment | Infrastructure | INFRA |
+
+### AC-ID Format by Project
+
+```
+AC-{PROJECT}-US{story}-{number}
+
+Examples:
+- AC-FE-US1-01 (Frontend, User Story 1, AC #1)
+- AC-BE-US1-01 (Backend, User Story 1, AC #1)
+- AC-SHARED-US1-01 (Shared, User Story 1, AC #1)
+- AC-MOBILE-US1-01 (Mobile, User Story 1, AC #1)
+```
+
+### tasks.md Must Reference Project-Scoped User Stories
+
+```markdown
+### T-001: Create Thumbnail Upload Component
+**User Story**: US-FE-001           ← MUST reference project-scoped ID!
+**Satisfies ACs**: AC-FE-US1-01, AC-FE-US1-02
+**Status**: [ ] Not Started
+
+### T-004: Database Schema & Migrations
+**User Story**: US-BE-001, US-BE-002   ← Backend stories only!
+**Satisfies ACs**: AC-BE-US1-01, AC-BE-US2-01
+**Status**: [ ] Not Started
+```
+
+### Workflow Summary
+
+```
+1. DETECT multi-project mode (check config.json, folder structure)
+   ↓
+2. If multi-project → Group user stories by project (FE/BE/SHARED/MOBILE/INFRA)
+   ↓
+3. Generate prefixed user stories: US-FE-001, US-BE-001, US-SHARED-001
+   ↓
+4. Generate prefixed ACs: AC-FE-US1-01, AC-BE-US1-01
+   ↓
+5. Generate tasks referencing correct project user stories
+   ↓
+6. Each project folder gets its own filtered spec
+```
+
+### Why This Matters
+
+Without project-scoped stories:
+- ❌ All issues created in ONE repo (wrong!)
+- ❌ No clarity which team owns what
+- ❌ Tasks reference wrong user stories
+- ❌ GitHub sync broken across repos
+
+With project-scoped stories:
+- ✅ Each repo gets only its user stories
+- ✅ Clear ownership per team/repo
+- ✅ GitHub issues in correct repo
+- ✅ Clean separation of concerns
+
+---
+
 ## Related Skills
 
 - **Planning workflow**: Guides increment planning (uses Spec Generator internally)
 - **Context loading**: Loads relevant context for specification generation
 - **Quality validation**: Validates generated specifications for completeness
+- **multi-project-spec-mapper**: Splits specs into project-specific files
+- **umbrella-repo-detector**: Detects multi-repo architecture
 
 ---
 
 ## Version History
 
+- **v2.0.0** (0.29.0): Added multi-project user story generation support
 - **v1.0.0** (0.8.0): Initial release with flexible template system
 - Based on: Flexible Spec Generator (V2) - context-aware, non-rigid templates

package/plugins/specweave/skills/umbrella-repo-detector/SKILL.md

@@ -0,0 +1,286 @@
+---
+name: umbrella-repo-detector
+description: Detects multi-repo architecture from user prompts and guides setup. Activates for: multiple repos, 3 repos, frontend repo, backend repo, shared library repo, monorepo services, microservices, separate repos, FE/BE/Shared, multi-repo architecture, independent repos.
+---
+
+# Umbrella Multi-Repo Architecture Detector
+
+## When This Skill Activates
+
+Activates when user describes:
+- Multiple repos: "3 repos", "frontend repo", "backend repo", "shared library"
+- Architecture patterns: "monorepo with services", "microservices", "multi-repo"
+- Explicit splits: "FE/BE/Shared", "frontend/backend/common"
+- GitHub URLs for multiple repositories
+
+## My Role
+
+When I detect a multi-repo architecture in the user's prompt:
+
+1. **Acknowledge the architecture** with detected repos
+2. **Explain project-scoped user stories** (US-FE-*, US-BE-*, US-SHARED-*)
+3. **Guide the init flow** for proper setup
+4. **Route to PM agent** with multi-repo context
+
+## Detection Patterns
+
+| Pattern | Example | Detected As |
+|---------|---------|-------------|
+| Repo count | "3 repos", "multiple repos" | Multi-repo intent |
+| Frontend repo | "Frontend repo", "UI repo", "web app" | Type: frontend, Prefix: FE |
+| Backend repo | "Backend API repo", "server", "API" | Type: backend, Prefix: BE |
+| Shared repo | "Shared library", "common types" | Type: shared, Prefix: SHARED |
+| Mobile repo | "Mobile app", "iOS/Android" | Type: mobile, Prefix: MOBILE |
+| Infra repo | "Infrastructure", "Terraform" | Type: infrastructure, Prefix: INFRA |
+
+## Project-Scoped User Stories
+
+When user describes multi-repo, user stories MUST be prefixed:
+
+```markdown
+## Instead of (generic):
+US-001: User Registration
+US-002: Registration API
+US-003: Validation Schema
+
+## Generate (project-scoped):
+US-FE-001: User Registration Form
+  - Related repo: frontend
+  - Keywords: form, UI, validation display
+
+US-BE-001: Registration API Endpoint
+  - Related repo: backend
+  - Keywords: API, endpoint, database
+
+US-SHARED-001: Registration Validation Schema
+  - Related repo: shared
+  - Keywords: validator, schema, types
+```
+
+## Cross-Cutting User Stories
+
+For features that span multiple repos, use cross-project tagging:
+
+```markdown
+US-AUTH-001: OAuth Integration
+  - Tags: ["cross-project", "frontend", "backend"]
+  - Creates linked issues in: FE repo, BE repo
+  - Child stories:
+    - US-FE-002: OAuth Login Button (frontend)
+    - US-BE-002: OAuth Token Validation (backend)
+```
+
+## Setup Flow Guidance
+
+When multi-repo detected, guide user through options:
+
+### Option 1: Clone from GitHub (Recommended)
+```
+You have existing repos? Let's clone them:
+1. Provide GitHub URLs (comma-separated or one per line)
+2. Each repo gets its own .specweave/ configuration
+3. Each repo syncs to its own GitHub issues
+```
+
+### Option 2: Create New Repos
+```
+Creating fresh repos:
+1. I'll create repos on GitHub for you
+2. Each gets initialized with .specweave/
+3. External tool sync configured per repo
+```
+
+### Option 3: Initialize Local Folders
+```
+Have local folders already?
+1. Point me to each folder
+2. I'll initialize .specweave/ in each
+3. Configure external tools per repo
+```
+
+## Umbrella Repo Structure
+
+```
+umbrella-project/                 # Optional parent repo
+├── .specweave/
+│   ├── config.json              # umbrella config with childRepos[]
+│   └── docs/                    # High-level PRD, roadmap only
+│
+├── my-app-fe/                   # Frontend repo (cloned/created)
+│   └── .specweave/
+│       ├── config.json          # sync → my-app-fe GitHub issues
+│       └── increments/
+│           └── 0001-feature/
+│               └── spec.md      # Only US-FE-* stories
+│
+├── my-app-be/                   # Backend repo (cloned/created)
+│   └── .specweave/
+│       └── ...                  # sync → my-app-be GitHub issues
+│
+└── my-app-shared/               # Shared repo (cloned/created)
+    └── .specweave/
+        └── ...                  # sync → my-app-shared GitHub issues
+```
+
+## Project ID Strategy
+
+**CRITICAL**: The `id` field MUST match your canonical source name - no arbitrary abbreviations!
+
+| Scenario | ID Source | Example |
+|----------|-----------|---------|
+| **1:1 Repo Mapping** | Exact repo name | `sw-qr-menu-fe` |
+| **JIRA Project** | Project key (lowercase) | `WEBAPP` → `webapp` |
+| **ADO Project** | Project name (kebab-case) | `Frontend Team` → `frontend-team` |
+| **Area Path** | Last segment (kebab-case) | `Product\Web` → `web` |
+
+```
+✅ CORRECT: id matches repo name
+   id: "sw-qr-menu-fe"
+   path: "./sw-qr-menu-fe"
+   githubUrl: "https://github.com/user/sw-qr-menu-fe"
+
+❌ WRONG: arbitrary abbreviation
+   id: "fe"              ← What if you have 2 frontend repos?
+   path: "./sw-qr-menu-fe"
+```
+
+**Note**: The `prefix` (for user stories like `US-FE-001`) can be short even if `id` is long:
+- `id: "sw-qr-menu-fe"` (full repo name)
+- `prefix: "FE"` (short, for user story IDs)
+
+## Config Example
+
+**Parent umbrella config** (`.specweave/config.json`):
+```json
+{
+  "umbrella": {
+    "enabled": true,
+    "childRepos": [
+      {
+        "id": "sw-qr-menu-fe",
+        "path": "./sw-qr-menu-fe",
+        "prefix": "FE",
+        "githubUrl": "https://github.com/myorg/sw-qr-menu-fe"
+      },
+      {
+        "id": "sw-qr-menu-be",
+        "path": "./sw-qr-menu-be",
+        "prefix": "BE",
+        "githubUrl": "https://github.com/myorg/sw-qr-menu-be"
+      },
+      {
+        "id": "sw-qr-menu-shared",
+        "path": "./sw-qr-menu-shared",
+        "prefix": "SHARED",
+        "githubUrl": "https://github.com/myorg/sw-qr-menu-shared"
+      }
+    ]
+  }
+}
+```
+
+**JIRA-based project** (when JIRA is source of truth):
+```json
+{
+  "umbrella": {
+    "enabled": true,
+    "childRepos": [
+      {
+        "id": "webapp",
+        "path": "./frontend",
+        "prefix": "WEBAPP",
+        "jiraProject": "WEBAPP",
+        "githubUrl": "https://github.com/myorg/frontend"
+      }
+    ]
+  }
+}
+```
+
+**Child repo config** (`sw-qr-menu-fe/.specweave/config.json`):
+```json
+{
+  "project": {
+    "name": "QR Menu Frontend",
+    "prefix": "FE"
+  },
+  "sync": {
+    "activeProfile": "github",
+    "profiles": {
+      "github": {
+        "provider": "github",
+        "config": {
+          "owner": "myorg",
+          "repo": "sw-qr-menu-fe"
+        }
+      }
+    }
+  }
+}
+```
+
+## Response Template
+
+When I detect multi-repo intent, respond:
+
+```
+I detected a **multi-repo architecture** in your description:
+
+**Detected Repos:**
+- Frontend (prefix: FE) - [matched keywords]
+- Backend (prefix: BE) - [matched keywords]
+- Shared (prefix: SHARED) - [matched keywords]
+
+**User Story Format:**
+User stories will be project-scoped:
+- `US-FE-001`: Frontend stories
+- `US-BE-001`: Backend stories
+- `US-SHARED-001`: Shared library stories
+
+**Setup Options:**
+1. **Clone from GitHub** - Provide URLs, I'll clone and initialize each
+2. **Create new repos** - I'll create on GitHub and initialize
+3. **Initialize local folders** - Point to existing folders
+
+Which would you like to do?
+```
+
+## Keywords for Story Routing
+
+| Keywords | Routes To | Prefix |
+|----------|-----------|--------|
+| UI, component, page, form, view, theme, drag-drop, builder | Frontend | FE |
+| API, endpoint, CRUD, webhook, notification, analytics | Backend | BE |
+| schema, validator, types, utilities, localization | Shared | SHARED |
+| iOS, Android, mobile, push notification | Mobile | MOBILE |
+| Terraform, K8s, Docker, CI/CD | Infrastructure | INFRA |
+
+## Saving Changes Across Repos
+
+Use `/specweave:save` to commit and push changes across all repos at once:
+
+```bash
+# Save all repos with same commit message
+/specweave:save "feat: Add user authentication"
+
+# Preview what would happen
+/specweave:save --dry-run
+
+# Save specific repos only
+/specweave:save "fix: Bug fixes" --repos frontend,backend
+```
+
+**Features:**
+- Auto-detects repos with changes
+- Sets up remotes if missing (prompts for URL or uses umbrella config)
+- Commits with same message to all repos
+- Pushes to origin
+- Skips repos with no changes
+
+## Important Notes
+
+1. **Each repo is independent** - Own `.specweave/`, own increments, own external tool sync
+2. **Parent repo is optional** - Can have umbrella config or just independent repos
+3. **User stories MUST have project prefix** - Never generate generic `US-001` in multi-repo mode
+4. **Cross-project stories get special handling** - Tagged and linked across repos
+5. **Use `/specweave:save`** - Single command to save changes across all repos

package/plugins/specweave-github/hooks/.specweave/logs/hooks-debug.log

@@ -1114,3 +1114,21 @@
 [Tue Nov 25 02:03:38 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
 [Tue Nov 25 02:03:39 EST 2025] [GitHub] 🔗 GitHub sync hook fired
 [Tue Nov 25 02:03:39 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 03:33:47 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 03:33:47 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 03:33:47 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 03:33:47 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 03:33:47 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 03:33:47 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 03:36:17 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 03:36:17 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 03:36:17 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 03:36:17 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 03:36:18 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 03:36:18 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 04:01:54 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 04:01:54 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 04:01:54 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 04:01:54 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Tue Nov 25 04:01:54 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Tue Nov 25 04:01:54 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync

package/plugins/specweave-infrastructure/skills/hetzner-provisioner/README.md

@@ -1,6 +1,6 @@
 **Name:** hetzner-provisioner
 **Type:** Infrastructure / DevOps
-**Model:** Claude Sonnet 4 (balanced for IaC generation)
+**Model:** Claude Sonnet 4.5 (balanced for IaC generation)
 **Status:** Planned
 
 ---

package/plugins/specweave-release/commands/specweave-release-npm.md

@@ -1,6 +1,6 @@
 ---
 name: specweave-release:npm
-description: Bump patch version, create git tag, and trigger npm publish via GitHub Actions. Automates the complete release workflow with pre-flight checks, version bumping, tag creation, and GitHub Actions triggering. Use --only flag for direct npm publish (skips git push and GitHub Actions).
+description: Bump patch version, create git tag, and trigger npm publish via GitHub Actions. Automates the complete release workflow with pre-flight checks, version bumping, tag creation, and GitHub Actions triggering. Use --only flag for quick local release (bumps version, builds, publishes to npm directly - NO git push, NO pipeline).
 ---
 
 # /specweave-release:npm - NPM Release Automation
@@ -9,8 +9,8 @@ You are the NPM Release Assistant. Your job is to automate the patch version rel
 
 ## Command Modes
 
-**Default mode** (no flags): Push to GitHub → GitHub Actions publishes to npm
-**Direct mode** (`--only`): Publish directly to npm (skip GitHub push/Actions)
+**Default mode** (no flags): Bump → Push to GitHub → GitHub Actions publishes to npm
+**Direct mode** (`--only`): Bump → Build → Publish to npm directly (NO git push, NO pipeline)
 
 ## Detecting Mode
 
@@ -186,16 +186,7 @@ npm publish
 - Publishes to npm registry immediately
 - No GitHub Actions involvement
 
-### 6. Push Git Changes (Optional but Recommended)
-
-```bash
-# Push the version bump commit and tag to GitHub
-git push origin develop --follow-tags
-```
-
-**Note**: This syncs GitHub with npm but does NOT trigger publish workflow (already published).
-
-### 7. Report Results (Direct Mode)
+### 6. Report Results (Direct Mode)
 
 Show the user:
 ```markdown
@@ -203,36 +194,37 @@ Show the user:
 
 📦 **Version**: vX.Y.Z
 🔗 **NPM**: https://www.npmjs.com/package/specweave
-🏷️ **Git Tag**: vX.Y.Z (created locally)
+🏷️ **Git Tag**: vX.Y.Z (local only)
 
 **What happened**:
-- ✅ Version bumped and committed
+- ✅ Version bumped and committed locally
 - ✅ Git tag created locally
 - ✅ Package built (npm run rebuild)
 - ✅ Published to npm directly
-- ✅ Git changes pushed to GitHub
+- ⏸️ Git NOT pushed (use `git push origin develop --follow-tags` later if needed)
 
 **Verify**:
 - Check npm: https://www.npmjs.com/package/specweave
 - Verify version: `npm view specweave version`
 - Install globally: `npm install -g specweave@X.Y.Z`
 
-**Note**: Published via direct push (bypassed GitHub Actions)
+**Note**: Local release only. Push to GitHub manually when ready:
+`git push origin develop --follow-tags`
 ```
 
 ## Direct Mode Safety Rules
 
 - ✅ ALWAYS rebuild before publishing (`npm run rebuild`)
-- ✅ ALWAYS push git changes after successful publish
-- ✅ Use `--only` for emergency releases or local testing
+- ✅ Use `--only` for emergency/quick releases or local testing
 - ✅ Default mode (GitHub Actions) is preferred for regular releases
 - ✅ Direct mode gives immediate feedback (no CI wait time)
+- ⚠️ Remember to push git changes later to sync GitHub
 
 ## Success Criteria (Direct Mode)
 
 ✅ Version bumped in package.json
-✅ Git commit created
-✅ Git tag created
+✅ Git commit created locally
+✅ Git tag created locally
 ✅ Package rebuilt
 ✅ Published to npm directly
-✅ Git changes pushed to GitHub (optional but recommended)
+⏸️ Git NOT pushed (manual sync later)

package/plugins/specweave-release/hooks/.specweave/logs/dora-tracking.log

@@ -1033,3 +1033,30 @@
 [2025-11-25 02:03:39] 🎯 Post-Increment-Completion Hook Triggered
 [2025-11-25 02:03:39] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
 [2025-11-25 02:03:39]    Run: npm run build
+[2025-11-25 03:33:47] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 03:33:47] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 03:33:47]    Run: npm run build
+[2025-11-25 03:33:47] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 03:33:47] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 03:33:47]    Run: npm run build
+[2025-11-25 03:33:47] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 03:33:47] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 03:33:47]    Run: npm run build
+[2025-11-25 03:36:17] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 03:36:17] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 03:36:17]    Run: npm run build
+[2025-11-25 03:36:18] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 03:36:18] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 03:36:18]    Run: npm run build
+[2025-11-25 03:36:18] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 03:36:18] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 03:36:18]    Run: npm run build
+[2025-11-25 04:01:54] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 04:01:54] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 04:01:54]    Run: npm run build
+[2025-11-25 04:01:54] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 04:01:54] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 04:01:54]    Run: npm run build
+[2025-11-25 04:01:54] 🎯 Post-Increment-Completion Hook Triggered
+[2025-11-25 04:01:54] ⚠️  DORA calculator not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-release/hooks/dist/src/metrics/dora-calculator.js
+[2025-11-25 04:01:54]    Run: npm run build