specweave 0.33.4 → 0.33.6

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

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado:clone-repos
+name: sw-ado:clone-repos
 description: Clone Azure DevOps repositories to local workspace. Use after init if cloning was skipped, or to add repos later.
 ---
 
@@ -19,19 +19,19 @@ This command clones Azure DevOps repositories **after** initial SpecWeave setup
 
 ```bash
 # Interactive mode (prompts for everything)
-/specweave-ado:clone-repos
+/sw-ado:clone-repos
 
 # With pattern filter
-/specweave-ado:clone-repos --pattern "sw-*"
+/sw-ado:clone-repos --pattern "sw-*"
 
 # Regex pattern
-/specweave-ado:clone-repos --pattern "regex:^api-.*$"
+/sw-ado:clone-repos --pattern "regex:^api-.*$"
 
 # Specific project only
-/specweave-ado:clone-repos --project "MyProject"
+/sw-ado:clone-repos --project "MyProject"
 
 # Dry-run (preview only)
-/specweave-ado:clone-repos --dry-run
+/sw-ado:clone-repos --dry-run
 ```
 
 ## Your Task
@@ -265,7 +265,7 @@ await triggerAdoRepoCloning(projectPath, adoProjectSelection, clonePatternResult
 ## Examples
 
 ### Example 1: Interactive Clone
-**User**: `/specweave-ado:clone-repos`
+**User**: `/sw-ado:clone-repos`
 
 **Output**:
 ```
@@ -319,12 +319,12 @@ Clone 16 repositories to current directory? (Y/n)
 
    ✓ Clone job started in background (PID: 12345)
 
-   Check progress: /specweave:jobs
-   Kill if needed: /specweave:jobs --kill abc12345
+   Check progress: /sw:jobs
+   Kill if needed: /sw:jobs --kill abc12345
 ```
 
 ### Example 2: Pattern Filter
-**User**: `/specweave-ado:clone-repos --pattern "sw-*"`
+**User**: `/sw-ado:clone-repos --pattern "sw-*"`
 
 **Output**:
 ```
@@ -345,7 +345,7 @@ Clone 8 repositories to current directory? (Y/n)
 ```
 
 ### Example 3: Dry Run
-**User**: `/specweave-ado:clone-repos --dry-run`
+**User**: `/sw-ado:clone-repos --dry-run`
 
 **Output**:
 ```
@@ -361,8 +361,8 @@ Clone 8 repositories to current directory? (Y/n)
 ## Important Notes
 
 - **Background Cloning**: Repositories clone in background (non-blocking)
-- **Progress Tracking**: Check progress with `/specweave:jobs`
-- **Resumable**: Interrupted clones can resume with `/specweave:jobs --resume <id>`
+- **Progress Tracking**: Check progress with `/sw:jobs`
+- **Resumable**: Interrupted clones can resume with `/sw:jobs --resume <id>`
 - **Auth via PAT**: Uses HTTPS clone URLs with PAT authentication
 - **Project-Based Folders**: Repos organized by ADO project: `./<project-name>/<repo-name>/`
   - Project names sanitized for filesystem (lowercase, spaces→hyphens)
@@ -370,16 +370,16 @@ Clone 8 repositories to current directory? (Y/n)
 
 ## Related Commands
 
-- `/specweave:init` - Initial SpecWeave setup (includes repo cloning option)
-- `/specweave:jobs` - Monitor background jobs
-- `/specweave-ado:import-projects` - Import ADO projects with area path mapping
+- `/sw:init` - Initial SpecWeave setup (includes repo cloning option)
+- `/sw:jobs` - Monitor background jobs
+- `/sw-ado:import-projects` - Import ADO projects with area path mapping
 
 ## Error Handling
 
 - **Missing Credentials**: Prompt to run `specweave init` first
 - **Auth Failures**: Check PAT permissions (vso.code_read scope required)
 - **Clone Failures**: Individual repo failures logged, others continue
-- **Network Errors**: Job pauses, resume with `/specweave:jobs --resume`
+- **Network Errors**: Job pauses, resume with `/sw:jobs --resume`
 
 ---
 

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

@@ -1,11 +1,11 @@
 ---
-name: specweave-ado:close
+name: sw-ado:close
 description: Close Azure DevOps work item when increment complete
 ---
 
 # Close ADO Work Item Command
 
-**Usage**: `/specweave-ado:close <increment-id>`
+**Usage**: `/sw-ado:close <increment-id>`
 
 **Purpose**: Close ADO work item and add completion summary
 
@@ -157,7 +157,7 @@ This command requires **both** permissions:
 ### Success
 
 ```
-User: /specweave-ado:close-workitem 0005-payment-integration
+User: /sw-ado:close-workitem 0005-payment-integration
 
 Claude:
 Checking permissions...
@@ -188,7 +188,7 @@ URL: https://dev.azure.com/acme-corp/My%20Project/_workitems/edit/12345
 ### Permission Denied
 
 ```
-User: /specweave-ado:close-workitem 0005
+User: /sw-ado:close-workitem 0005
 
 Claude:
 Checking permissions...
@@ -207,7 +207,7 @@ Update .specweave/config.json to enable these permissions.
 ### Incomplete Increment
 
 ```
-User: /specweave-ado:close-workitem 0005
+User: /sw-ado:close-workitem 0005
 
 Claude:
 Checking permissions...
@@ -234,8 +234,8 @@ Complete remaining tasks:
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:pull` | Pull changes from ADO |
-| `/specweave-ado:push` | Push progress to ADO |
-| `/specweave-ado:sync` | Two-way sync |
-| `/specweave-ado:create` | Create ADO work item |
-| `/specweave-ado:status` | Check sync status |
+| `/sw-ado:pull` | Pull changes from ADO |
+| `/sw-ado:push` | Push progress to ADO |
+| `/sw-ado:sync` | Two-way sync |
+| `/sw-ado:create` | Create ADO work item |
+| `/sw-ado:status` | Check sync status |

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

@@ -1,11 +1,11 @@
 ---
-name: specweave-ado:create
+name: sw-ado:create
 description: Create Azure DevOps work item from SpecWeave increment
 ---
 
 # Create ADO Work Item Command
 
-**Usage**: `/specweave-ado:create <increment-id>`
+**Usage**: `/sw-ado:create <increment-id>`
 
 **Purpose**: Create an Epic, Feature, or User Story in Azure DevOps from a SpecWeave increment
 
@@ -142,7 +142,7 @@ This setting was configured during 'specweave init'.
 ## Example Usage
 
 ```
-User: /specweave-ado:create-workitem 0005-payment-integration
+User: /sw-ado:create-workitem 0005-payment-integration
 
 # If permission granted:
 Claude: Checking ADO permissions...
@@ -174,8 +174,8 @@ Claude: Checking ADO permissions...
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:pull` | Pull changes from ADO |
-| `/specweave-ado:push` | Push progress to ADO |
-| `/specweave-ado:sync` | Two-way sync |
-| `/specweave-ado:status` | Check sync status |
-| `/specweave-ado:close` | Close work item when complete |
+| `/sw-ado:pull` | Pull changes from ADO |
+| `/sw-ado:push` | Push progress to ADO |
+| `/sw-ado:sync` | Two-way sync |
+| `/sw-ado:status` | Check sync status |
+| `/sw-ado:close` | Close work item when complete |

package/plugins/specweave-ado/commands/import-areas.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado:import-areas
+name: sw-ado:import-areas
 description: Import Azure DevOps area paths from a project and map them to SpecWeave projects. Creates 2-level directory structure with area path-based organization.
 ---
 
@@ -10,10 +10,10 @@ You are an Azure DevOps integration expert. Help the user import area paths from
 ## Command Usage
 
 ```bash
-/specweave-ado:import-areas                         # Interactive mode (prompts for project)
-/specweave-ado:import-areas --project MyProduct     # Specific ADO project
-/specweave-ado:import-areas --dry-run               # Preview without creating directories
-/specweave-ado:import-areas --include-children      # Include child area paths
+/sw-ado:import-areas                         # Interactive mode (prompts for project)
+/sw-ado:import-areas --project MyProduct     # Specific ADO project
+/sw-ado:import-areas --dry-run               # Preview without creating directories
+/sw-ado:import-areas --include-children      # Include child area paths
 ```
 
 ## Your Task
@@ -226,8 +226,8 @@ Area paths imported:
     Keywords: infrastructure, ci, cd, terraform
 
 💡 Next steps:
-  1. Use /specweave:switch-project fe to switch active project
-  2. Create increment: /specweave:increment "feature name"
+  1. Use /sw:switch-project fe to switch active project
+  2. Create increment: /sw:increment "feature name"
   3. User stories will auto-sync to the correct area path based on keywords
 
 📖 Documentation: .specweave/docs/internal/architecture/adr/0143-jira-ado-multi-level-project-mapping.md
@@ -237,7 +237,7 @@ Area paths imported:
 
 ### Example 1: Interactive Import
 ```
-User: /specweave-ado:import-areas
+User: /sw-ado:import-areas
 
 You:
 🔷 Azure DevOps Area Path Import
@@ -261,7 +261,7 @@ Mapping to SpecWeave projects:
 
 ### Example 2: Dry Run
 ```
-User: /specweave-ado:import-areas --project MyProduct --dry-run
+User: /sw-ado:import-areas --project MyProduct --dry-run
 
 You:
 🔷 Azure DevOps Area Path Import (DRY RUN)
@@ -281,7 +281,7 @@ No changes made (dry run).
 
 ### Example 3: Already Configured
 ```
-User: /specweave-ado:import-areas
+User: /sw-ado:import-areas
 
 You:
 ⚠️  Area path mapping already exists for project MyProduct
@@ -333,7 +333,7 @@ Available projects you have access to:
   - Infrastructure (DevOps & Infrastructure)
   - Legacy (Legacy Systems)
 
-Tip: Use /specweave-ado:import-areas --project MyProduct
+Tip: Use /sw-ado:import-areas --project MyProduct
 ```
 
 **No area paths found:**
@@ -352,7 +352,7 @@ Suggestions:
 
 ## Related Commands
 
-- `/specweave-ado:import-projects` - Import multiple ADO projects
-- `/specweave-ado:sync` - Sync increments with ADO
-- `/specweave:switch-project` - Switch active SpecWeave project
-- `/specweave:init-multiproject` - Initialize multi-project mode
+- `/sw-ado:import-projects` - Import multiple ADO projects
+- `/sw-ado:sync` - Sync increments with ADO
+- `/sw:switch-project` - Switch active SpecWeave project
+- `/sw:init-multiproject` - Initialize multi-project mode

package/plugins/specweave-ado/commands/import-projects.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado:import-projects
+name: sw-ado:import-projects
 description: Import additional Azure DevOps projects post-init with area path mapping, filtering, and dry-run preview
 ---
 
@@ -21,19 +21,19 @@ This command allows users to import additional Azure DevOps projects **after** i
 
 ```bash
 # Basic import (interactive)
-/specweave-ado:import-projects
+/sw-ado:import-projects
 
 # With area path granularity
-/specweave-ado:import-projects --granularity two-level
+/sw-ado:import-projects --granularity two-level
 
 # Dry-run (preview)
-/specweave-ado:import-projects --dry-run
+/sw-ado:import-projects --dry-run
 
 # Resume interrupted import
-/specweave-ado:import-projects --resume
+/sw-ado:import-projects --resume
 
 # Combined
-/specweave-ado:import-projects --granularity top-level --dry-run
+/sw-ado:import-projects --granularity top-level --dry-run
 ```
 
 ## Your Task
@@ -228,7 +228,7 @@ if (args.resume) {
 ## Examples
 
 ### Example 1: Basic Import with Area Paths
-**User**: `/specweave-ado:import-projects`
+**User**: `/sw-ado:import-projects`
 
 **Output**:
 ```
@@ -277,7 +277,7 @@ Area paths configured:
 ```
 
 ### Example 2: Top-Level Only
-**User**: `/specweave-ado:import-projects --granularity top-level`
+**User**: `/sw-ado:import-projects --granularity top-level`
 
 **Output**:
 ```
@@ -291,7 +291,7 @@ Select area path granularity: top-level (forced via CLI)
 ```
 
 ### Example 3: Dry-Run
-**User**: `/specweave-ado:import-projects --dry-run`
+**User**: `/sw-ado:import-projects --dry-run`
 
 **Output**:
 ```
@@ -315,9 +315,9 @@ Total: 8 projects would be configured
 
 ## Related Commands
 
-- `/specweave:init` - Initial SpecWeave setup
-- `/specweave-ado:sync` - Sync increments with ADO work items
-- `/specweave-ado:refresh-cache` - Clear cached ADO data
+- `/sw:init` - Initial SpecWeave setup
+- `/sw-ado:sync` - Sync increments with ADO work items
+- `/sw-ado:refresh-cache` - Clear cached ADO data
 
 ## Error Handling
 

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

@@ -1,11 +1,11 @@
 ---
-name: specweave-ado:pull
+name: sw-ado:pull
 description: Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
 ---
 
 # ADO Pull Command
 
-**Usage**: `/specweave-ado:pull [target] [options]`
+**Usage**: `/sw-ado:pull [target] [options]`
 
 **Purpose**: Pull latest changes from Azure DevOps (like `git pull`)
 
@@ -15,19 +15,19 @@ description: Pull latest changes from Azure DevOps (like git pull). Supports inc
 
 ```bash
 # Pull for current/active increment (simple mode)
-/specweave-ado:pull
+/sw-ado:pull
 
 # Pull for specific increment
-/specweave-ado:pull 0005
+/sw-ado:pull 0005
 
 # Pull ALL changes across ALL projects (living docs sync)
-/specweave-ado:pull --all
+/sw-ado:pull --all
 
 # Pull for specific project/board
-/specweave-ado:pull --project clinical-insights
+/sw-ado:pull --project clinical-insights
 
 # Pull specific feature hierarchy (Epic → Feature → User Stories)
-/specweave-ado:pull --feature FS-042
+/sw-ado:pull --feature FS-042
 ```
 
 ---
@@ -36,13 +36,13 @@ description: Pull latest changes from Azure DevOps (like git pull). Supports inc
 
 ### Mode 1: Increment Sync (Default)
 ```bash
-/specweave-ado:pull [increment-id]
+/sw-ado:pull [increment-id]
 ```
 Syncs ONE increment ↔ ONE linked work item.
 
 ### Mode 2: Living Docs Sync (Full)
 ```bash
-/specweave-ado:pull --all [--time-range 1M]
+/sw-ado:pull --all [--time-range 1M]
 ```
 Syncs ALL specs across ALL projects/boards:
 - Discovers all linked specs in `.specweave/docs/internal/specs/`
@@ -52,7 +52,7 @@ Syncs ALL specs across ALL projects/boards:
 
 ### Mode 3: Project-Scoped Sync
 ```bash
-/specweave-ado:pull --project clinical-insights
+/sw-ado:pull --project clinical-insights
 ```
 Syncs all specs within a specific project folder:
 ```
@@ -64,7 +64,7 @@ specs/clinical-insights/
 
 ### Mode 4: Feature Hierarchy Sync
 ```bash
-/specweave-ado:pull --feature FS-042
+/sw-ado:pull --feature FS-042
 ```
 Syncs a specific feature and ALL its children:
 ```
@@ -136,7 +136,7 @@ const metadata = await loadIncrementMetadata(incrementId);
 
 const adoWorkItemId = metadata?.external_sync?.ado?.workItemId;
 if (!adoWorkItemId) {
-  console.log('Not linked to ADO. Run: /specweave-ado:create');
+  console.log('Not linked to ADO. Run: /sw-ado:create');
   return;
 }
 
@@ -220,7 +220,7 @@ async function discoverLinkedSpecs(options) {
 ### Example 1: Pull Single Increment
 
 ```
-User: /specweave-ado:pull 0005
+User: /sw-ado:pull 0005
 
 Claude:
 Pulling from ADO...
@@ -236,7 +236,7 @@ Pull complete!
 ### Example 2: Pull All (Living Docs Sync)
 
 ```
-User: /specweave-ado:pull --all
+User: /sw-ado:pull --all
 
 Claude:
 Discovering linked specs...
@@ -266,7 +266,7 @@ Pull Summary:
 ### Example 3: Pull Specific Project
 
 ```
-User: /specweave-ado:pull --project clinical-insights
+User: /sw-ado:pull --project clinical-insights
 
 Claude:
 Pulling specs/clinical-insights/...
@@ -282,7 +282,7 @@ Pull complete! 2 specs updated.
 ### Example 4: Pull Feature Hierarchy
 
 ```
-User: /specweave-ado:pull --feature FS-042
+User: /sw-ado:pull --feature FS-042
 
 Claude:
 Fetching ADO hierarchy for FS-042...
@@ -323,7 +323,7 @@ This ensures QA and stakeholder decisions in ADO take precedence over local stat
 ### Example 1: Simple Pull
 
 ```
-User: /specweave-ado:pull
+User: /sw-ado:pull
 
 Claude:
 Pulling from ADO...
@@ -339,7 +339,7 @@ Pull complete!
 ### Example 2: No Changes
 
 ```
-User: /specweave-ado:pull 0005
+User: /sw-ado:pull 0005
 
 Claude:
 Pulling from ADO...
@@ -353,12 +353,12 @@ Last synced: 2 minutes ago
 ### Example 3: Not Linked
 
 ```
-User: /specweave-ado:pull 0005
+User: /sw-ado:pull 0005
 
 Claude:
 Increment 0005 not linked to ADO yet.
 
-To link: /specweave-ado:create 0005
+To link: /sw-ado:create 0005
 ```
 
 ---
@@ -445,7 +445,7 @@ To link: /specweave-ado:create 0005
 │    ⚠ FS-042/us-003: ADO item #205 not found (deleted?) │
 │    ⚠ FS-050/us-012: Rate limit hit, skipped            │
 ├─────────────────────────────────────────────────────────┤
-│  Retry failed items: /specweave-ado:pull --retry        │
+│  Retry failed items: /sw-ado:pull --retry        │
 └─────────────────────────────────────────────────────────┘
 ```
 
@@ -483,7 +483,7 @@ AZURE_DEVOPS_PAT=your-personal-access-token
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:push` | Push local changes to ADO |
-| `/specweave-ado:sync` | Two-way sync (pull + push) |
-| `/specweave-ado:status` | Check sync status |
-| `/specweave-ado:create` | Create ADO work item |
+| `/sw-ado:push` | Push local changes to ADO |
+| `/sw-ado:sync` | Two-way sync (pull + push) |
+| `/sw-ado:status` | Check sync status |
+| `/sw-ado:create` | Create ADO work item |

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

@@ -1,11 +1,11 @@
 ---
-name: specweave-ado:push
+name: sw-ado:push
 description: Push local changes to Azure DevOps (like git push). Supports increment, project, or full living docs sync.
 ---
 
 # ADO Push Command
 
-**Usage**: `/specweave-ado:push [target] [options]`
+**Usage**: `/sw-ado:push [target] [options]`
 
 **Purpose**: Push local changes to Azure DevOps (like `git push`)
 
@@ -15,19 +15,19 @@ description: Push local changes to Azure DevOps (like git push). Supports increm
 
 ```bash
 # Push current/active increment (simple mode)
-/specweave-ado:push
+/sw-ado:push
 
 # Push specific increment
-/specweave-ado:push 0005
+/sw-ado:push 0005
 
 # Push ALL local changes to ADO (living docs sync)
-/specweave-ado:push --all
+/sw-ado:push --all
 
 # Push specific project/board
-/specweave-ado:push --project clinical-insights
+/sw-ado:push --project clinical-insights
 
 # Push specific feature hierarchy
-/specweave-ado:push --feature FS-042
+/sw-ado:push --feature FS-042
 ```
 
 ---
@@ -97,7 +97,7 @@ To enable writes, update .specweave/config.json:
   "sync": { "settings": { "canUpdateExternalItems": true } }
 
 Or use read-only mode:
-  /specweave-ado:pull ${incrementId}
+  /sw-ado:pull ${incrementId}
 `);
   return;
 }
@@ -114,7 +114,7 @@ const metadata = JSON.parse(await fs.readFile(
 
 const adoWorkItemId = metadata?.external_sync?.ado?.workItemId;
 if (!adoWorkItemId) {
-  console.log(`Not linked to ADO. Run: /specweave-ado:create ${incrementId}`);
+  console.log(`Not linked to ADO. Run: /sw-ado:create ${incrementId}`);
   return;
 }
 
@@ -204,7 +204,7 @@ If `canUpdateStatus` is false, progress is posted but state unchanged.
 ### Example 1: Simple Push
 
 ```
-User: /specweave-ado:push
+User: /sw-ado:push
 
 Claude:
 Checking permissions...
@@ -225,7 +225,7 @@ Push complete!
 ### Example 2: Permission Denied
 
 ```
-User: /specweave-ado:push 0005
+User: /sw-ado:push 0005
 
 Claude:
 Checking permissions...
@@ -237,13 +237,13 @@ To enable ADO writes:
 1. Edit .specweave/config.json
 2. Set sync.settings.canUpdateExternalItems = true
 
-Or use read-only: /specweave-ado:pull 0005
+Or use read-only: /sw-ado:pull 0005
 ```
 
 ### Example 3: 100% Complete
 
 ```
-User: /specweave-ado:push 0005
+User: /sw-ado:push 0005
 
 Claude:
 Pushing to ADO...
@@ -256,7 +256,7 @@ Comment posted:
 State updated:
   Active -> Resolved (canUpdateStatus = true)
 
-Ready to close: /specweave-ado:close 0005
+Ready to close: /sw-ado:close 0005
 ```
 
 ---
@@ -330,7 +330,7 @@ Ready to close: /specweave-ado:close 0005
 │    ↑ Status: Active → Resolved                          │
 ├─────────────────────────────────────────────────────────┤
 │  🎉 INCREMENT READY TO CLOSE                            │
-│     Run: /specweave-ado:close 0005                      │
+│     Run: /sw-ado:close 0005                      │
 └─────────────────────────────────────────────────────────┘
 ```
 
@@ -347,7 +347,7 @@ Ready to close: /specweave-ado:close 0005
 │    sync.settings.canUpdateExternalItems = true          │
 │                                                         │
 │  OR USE READ-ONLY:                                      │
-│    /specweave-ado:pull 0005                             │
+│    /sw-ado:pull 0005                             │
 └─────────────────────────────────────────────────────────┘
 ```
 
@@ -385,7 +385,7 @@ AZURE_DEVOPS_PAT=your-personal-access-token
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:pull` | Pull changes from ADO |
-| `/specweave-ado:sync` | Two-way sync (pull + push) |
-| `/specweave-ado:status` | Check sync status |
-| `/specweave-ado:close` | Close completed work item |
+| `/sw-ado:pull` | Pull changes from ADO |
+| `/sw-ado:sync` | Two-way sync (pull + push) |
+| `/sw-ado:status` | Check sync status |
+| `/sw-ado:close` | Close completed work item |

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

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado:reconcile
+name: sw-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.
 ---
 
@@ -10,7 +10,7 @@ Scan all increments and fix any drift between local metadata.json status and ADO
 ## Usage
 
 ```bash
-/specweave-ado:reconcile [options]
+/sw-ado:reconcile [options]
 ```
 
 ## Options
@@ -81,7 +81,7 @@ if (result.errors.length > 0) {
 ## Dry Run Mode
 
 ```bash
-/specweave-ado:reconcile --dry-run
+/sw-ado:reconcile --dry-run
 ```
 
 Shows what would be changed without making any modifications:
@@ -114,7 +114,7 @@ Shows what would be changed without making any modifications:
 
 ## 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)
+- `/sw-ado:status`: View sync status for increments
+- `/sw-ado:sync`: Manual sync to ADO
+- `/sw:done`: Close increment (triggers auto-close)
+- `/sw:resume`: Resume increment (now triggers auto-reopen)