jettypod 4.4.19 → 4.4.22

package/lib/work-commands/work-commands.feature

@@ -0,0 +1,13 @@
+Feature: Work Item Commands
+  As a developer
+  I want to start and stop work on items
+  So that my current work is tracked automatically
+
+  Scenario: Integration - work commands with existing work tracking
+    Given I have initialized jettypod
+    And I create an epic with id 1
+    And I create a feature with id 2 under epic 1
+    When I start work on item 2
+    Then the current work file exists
+    And the current work contains item 2
+    And item 2 status is in_progress or backlog

package/lib/work-commands/worktree-management.feature

@@ -0,0 +1,63 @@
+@worktree
+Feature: Worktree-based Branch Management
+  As a developer using JettyPod with multiple Claude instances
+  I want work items to use git worktrees
+  So that multiple Claude instances can work in parallel without conflicts
+
+  Background:
+    Given I am on the main branch
+
+  Scenario: Start work creates a worktree
+    Given I have a work item with ID 1
+    When I start worktree work on item 1
+    Then a worktree should be created at ".jettypod-work/1-*"
+    And the worktree should be on branch "feature/work-1-*"
+    And the main directory should remain on "main" branch
+
+  Scenario: Worktree has symlink to shared .jettypod directory
+    Given I have a work item with ID 1
+    When I start worktree work on item 1
+    Then the worktree should have a symlink ".jettypod" pointing to shared metadata
+    And the worktree should have its own CLAUDE.md with work item context
+
+  Scenario: Complete work without conflicts merges and cleans up
+    Given I have a work item with ID 1 in a worktree
+    And I have made commits in the worktree
+    And there are no conflicts with main
+    When I stop work on item 1 with status "done"
+    Then the worktree branch should be merged to main
+    And the worktree should be removed
+    And the worktree branch should be deleted
+    And I should be on the main branch
+
+  Scenario: Completing work with conflicts detects them before merge
+    Given I have a work item with ID 1 in a worktree
+    And I have modified "lib/auth.js" in the worktree
+    And someone else has modified "lib/auth.js" in main
+    When I stop work on item 1 with status "done"
+    Then I should see a conflict detection message
+    And the merge should not be attempted
+    And the worktree should be preserved for conflict resolution
+
+  Scenario: Multiple work items can be in progress simultaneously
+    Given I have work items with IDs 1, 2, and 3
+    When I start worktree work on item 1
+    And I start worktree work on item 2
+    And I start worktree work on item 3
+    Then worktree ".jettypod-work/1-*" should exist
+    And worktree ".jettypod-work/2-*" should exist
+    And worktree ".jettypod-work/3-*" should exist
+    And each worktree should be on its own feature branch
+
+  Scenario: Stop work without done status preserves worktree
+    Given I have a work item with ID 1 in a worktree
+    When I stop work on item 1 with status "blocked"
+    Then the work item should have status "blocked" in database
+    And the worktree should be preserved
+    And the worktree branch should not be deleted
+
+  Scenario: Worktree path is tracked in database
+    Given I have a work item with ID 1
+    When I start worktree work on item 1
+    Then the work item should have worktree_path in database
+    And the worktree_path should point to ".jettypod-work/1-*"