jettypod 4.4.19 → 4.4.22

package/lib/work-tracking/mode-required.feature

@@ -0,0 +1,111 @@
+Feature: Work item mode handling
+  As a developer
+  I want features to support speed/stable/production modes
+  So I can work in the appropriate mode for each phase
+
+  # Epic scenarios - epics don't have mode
+  Scenario: Create epic without mode
+    Given jettypod is initialized
+    When I create an epic "Test Epic" without mode
+    Then the work item is created successfully
+    And the work item has NULL mode
+
+  Scenario: Create epic with mode (optional)
+    Given jettypod is initialized
+    When I create an epic "Test Epic" with mode "stable"
+    Then the work item is created successfully
+    And the work item has mode "stable"
+
+  # Feature scenarios - mode is optional
+  Scenario: Create feature with explicit mode
+    Given jettypod is initialized
+    When I create a feature "Test Feature" with mode "speed"
+    Then the work item is created successfully
+    And the work item has mode "speed"
+
+  Scenario: Create feature without mode has NULL mode
+    Given jettypod is initialized
+    When I create a feature "Test Feature" without mode
+    Then the work item is created successfully
+    And the work item has NULL mode
+
+  Scenario: Create feature with invalid mode
+    Given jettypod is initialized
+    When I try to create a feature "Test Feature" with mode "invalid"
+    Then I get an error "Invalid mode"
+    And no work item is created
+
+  # Bug scenarios - bugs don't have modes
+  Scenario: Create bug with mode fails
+    Given jettypod is initialized
+    When I try to create a bug "Test Bug" with mode "stable"
+    Then I get an error "Bugs cannot have modes"
+    And no work item is created
+
+  Scenario: Create bug without mode succeeds with NULL
+    Given jettypod is initialized
+    When I create a bug "Test Bug" without mode
+    Then the work item is created successfully
+    And the work item has no mode
+
+  # Chore scenarios - chores don't have modes
+  Scenario: Create chore with mode fails
+    Given jettypod is initialized
+    When I try to create a chore "Test Chore" with mode "production"
+    Then I get an error "Chores do not have modes"
+    And no work item is created
+
+  Scenario: Create chore without mode succeeds with NULL
+    Given jettypod is initialized
+    When I create a chore "Test Chore" without mode
+    Then the work item is created successfully
+    And the work item has NULL mode
+
+  # All valid modes
+  Scenario Outline: Create feature with all valid modes
+    Given jettypod is initialized
+    When I create a feature "Test Feature" with mode "<mode>"
+    Then the work item is created successfully
+    And the work item has mode "<mode>"
+
+    Examples:
+      | mode       |
+      | speed      |
+      | stable     |
+      | production |
+
+  # Integration - hierarchical structure
+  Scenario: Epic with children in different modes
+    Given jettypod is initialized
+    And I create an epic "Test Epic" without mode
+    And I create a feature "Speed Feature" with mode "speed" and parent epic
+    And I create a bug "Test Bug" with parent epic
+    And I create a chore "Test Chore" without mode and parent epic
+    When I view the backlog
+    Then I see the epic without mode indicator
+    And I see the feature with mode "speed"
+    And I see the bug without mode indicator
+    And I see the chore without mode indicator
+
+  # Edge cases
+  Scenario: Create multiple items with same title but different modes
+    Given jettypod is initialized
+    When I create a feature "Duplicate" with mode "speed"
+    And I create a feature "Duplicate" with mode "stable"
+    Then both work items are created successfully
+    And they have different modes
+
+  Scenario: Mode is case-sensitive
+    Given jettypod is initialized
+    When I try to create a feature "Test" with mode "Speed"
+    Then I get an error "Invalid mode"
+
+  Scenario: Mode with whitespace is invalid
+    Given jettypod is initialized
+    When I try to create a feature "Test" with mode " speed "
+    Then I get an error "Invalid mode"
+
+  Scenario: Empty string mode is treated as NULL
+    Given jettypod is initialized
+    When I try to create a feature "Test" with mode ""
+    Then I get an error "Invalid mode"

package/lib/work-tracking/work-set-mode.feature

@@ -0,0 +1,70 @@
+Feature: Work set-mode updates CLAUDE.md if item is current
+  As a developer
+  I want to change a work item's mode with jettypod work set-mode
+  So I can adjust my approach without recreating the work item
+
+  Background:
+    Given jettypod is initialized
+    And CLAUDE.md exists
+
+  # Basic mode changes
+  Scenario: Set mode on current work item updates CLAUDE.md
+    Given I create a feature "Test Feature" with mode "speed"
+    And I start work on the feature
+    And CLAUDE.md mode is set to "speed"
+    When I set mode for current item to "stable"
+    Then the work item has mode "stable"
+    And CLAUDE.md mode is set to "stable"
+
+  Scenario: Set mode on non-current item does not update CLAUDE.md
+    Given I create a feature "Item 1" with mode "speed"
+    And I create a feature "Item 2" with mode "stable"
+    And I start work on the feature "Item 1"
+    And CLAUDE.md mode is set to "speed"
+    When I set mode for item "Item 2" to "production"
+    Then item "Item 2" has mode "production"
+    But CLAUDE.md mode is set to "speed"
+
+  # Mode validation
+  Scenario: Set invalid mode shows error
+    Given I create a feature "Test Feature" with mode "speed"
+    When I try to set mode to "invalid"
+    Then I get error "Invalid mode"
+    And the work item still has mode "speed"
+
+  Scenario: Set mode is case-sensitive
+    Given I create a feature "Test Feature" with mode "speed"
+    When I try to set mode to "Speed"
+    Then I get error "Invalid mode"
+
+  # All valid modes
+  Scenario Outline: Change to all valid modes
+    Given I create a feature "Test Feature" with mode "speed"
+    And I start work on the feature
+    When I set mode for current item to "<new_mode>"
+    Then the work item has mode "<new_mode>"
+    And CLAUDE.md mode is set to "<new_mode>"
+
+    Examples:
+      | new_mode   |
+      | stable     |
+      | production |
+
+  # Mode persistence
+  Scenario: Mode change persists across work start/stop
+    Given I create a feature "Test Feature" with mode "speed"
+    And I start work on the feature
+    When I set mode for current item to "production"
+    And I stop work
+    And I start work on the feature
+    Then CLAUDE.md mode is set to "production"
+
+  # Multiple mode changes
+  Scenario: Change mode multiple times
+    Given I create a feature "Test Feature" with mode "speed"
+    And I start work on the feature
+    When I set mode for current item to "stable"
+    And I set mode for current item to "production"
+    And I set mode for current item to "speed"
+    Then the work item has mode "speed"
+    And CLAUDE.md mode is set to "speed"

package/lib/work-tracking/work-start-mode.feature

@@ -0,0 +1,83 @@
+Feature: Work start sets CLAUDE.md mode from work item
+  As a developer
+  I want jettypod work start to set the CLAUDE.md mode from the work item's mode
+  So I automatically work in the correct mode for each work item
+
+  Background:
+    Given jettypod is initialized
+    And CLAUDE.md exists
+
+  # Basic mode inheritance
+  Scenario: Start work on feature in speed mode
+    Given I create a feature "Speed Feature" with mode "speed"
+    When I start work on the feature
+    Then CLAUDE.md mode is set to "speed"
+
+  Scenario: Start work on chore inherits parent feature mode
+    Given I create a feature "Speed Feature" with mode "speed"
+    And I create a chore "Child Chore" without mode and parent feature
+    When I start work on the chore
+    Then CLAUDE.md mode is set to "speed"
+
+  Scenario: Start work on feature in production mode
+    Given I create a feature "Production Feature" with mode "production"
+    When I start work on the feature
+    Then CLAUDE.md mode is set to "production"
+
+  # Mode switching between work items
+  Scenario: Switch from speed mode item to stable mode item
+    Given I create a feature "Speed Feature" with mode "speed"
+    And I create a feature "Stable Feature" with mode "stable"
+    And I start work on the feature "Speed Feature"
+    And CLAUDE.md mode is set to "speed"
+    When I stop work
+    And I start work on the feature "Stable Feature"
+    Then CLAUDE.md mode is set to "stable"
+
+  Scenario: Start work updates mode even if item already in progress
+    Given I create a feature "Test Feature" with mode "stable"
+    And the feature status is "in_progress"
+    And CLAUDE.md has mode "speed"
+    When I start work on the feature
+    Then CLAUDE.md mode is set to "stable"
+
+  # Epic handling - epics don't have modes
+  Scenario: Start work on epic (NULL mode)
+    Given I create an epic "Test Epic" without mode
+    When I start work on the epic
+    Then CLAUDE.md has no mode line
+    And the current work section exists
+
+  # NULL mode handling
+  Scenario: Start work on feature without mode (NULL)
+    Given I create a feature "Default Feature" without mode
+    And the work item has NULL mode
+    When I start work on the feature
+    Then CLAUDE.md has no mode line
+
+  # Hierarchical structure
+  Scenario: Start work on child features use their own mode, not parent's
+    Given I create an epic "Test Epic" without mode
+    And I create a feature "Speed Feature" with mode "speed" and parent epic
+    And I create a feature "Stable Feature" with mode "stable" and parent epic
+    When I start work on the speed feature
+    Then CLAUDE.md mode is set to "speed"
+    When I stop work
+    And I start work on the stable feature
+    Then CLAUDE.md mode is set to "stable"
+
+  # Mode persistence
+  Scenario: Work item mode persists in database after start
+    Given I create a feature "Test Feature" with mode "stable"
+    When I start work on the feature
+    And I stop work
+    Then the work item still has mode "stable"
+
+  # Edge cases
+  Scenario: Starting work multiple times preserves mode
+    Given I create a feature "Test Feature" with mode "production"
+    When I start work on the feature
+    And I stop work
+    And I start work on the feature
+    Then CLAUDE.md mode is set to "production"
+    And the work item still has mode "production"

package/lib/worktree-manager.js

@@ -231,28 +231,34 @@ async function createWorktree(workItem, options = {}) {
       throw new Error(`Failed to create .jettypod symlink: ${symlinkErr.message}`);
     }
 
-    // Step 4.5: Add .jettypod to worktree's .gitignore
-    // NOTE: git's info/exclude does NOT work for worktrees - only .gitignore works
+    // Step 4.5: Add .jettypod to MAIN repo's .git/info/exclude
+    // NOTE: Worktree-specific info/exclude does NOT work - must use main repo's exclude
     // This prevents the symlink from being committed when merging the worktree branch
     try {
-      const gitignorePath = path.join(worktreePath, '.gitignore');
+      const excludePath = path.join(gitRoot, '.git', 'info', 'exclude');
 
-      // Read existing .gitignore or create empty
-      let gitignoreContent = '';
-      if (fs.existsSync(gitignorePath)) {
-        gitignoreContent = fs.readFileSync(gitignorePath, 'utf8');
+      // Ensure the info directory exists
+      const infoDir = path.dirname(excludePath);
+      if (!fs.existsSync(infoDir)) {
+        fs.mkdirSync(infoDir, { recursive: true });
       }
 
-      // Add .jettypod if not already in .gitignore
-      if (!gitignoreContent.includes('.jettypod')) {
-        const newEntry = gitignoreContent.endsWith('\n') || gitignoreContent === ''
+      // Read existing exclude or create empty
+      let excludeContent = '';
+      if (fs.existsSync(excludePath)) {
+        excludeContent = fs.readFileSync(excludePath, 'utf8');
+      }
+
+      // Add .jettypod if not already excluded
+      if (!excludeContent.includes('.jettypod')) {
+        const newEntry = excludeContent.endsWith('\n') || excludeContent === ''
           ? '.jettypod\n'
           : '\n.jettypod\n';
-        fs.writeFileSync(gitignorePath, gitignoreContent + newEntry);
+        fs.writeFileSync(excludePath, excludeContent + newEntry);
       }
-    } catch (gitignoreErr) {
+    } catch (excludeErr) {
       // Non-fatal - log warning but continue
-      console.warn(`Warning: Could not add .jettypod to .gitignore: ${gitignoreErr.message}`);
+      console.warn(`Warning: Could not add .jettypod to .git/info/exclude: ${excludeErr.message}`);
     }
 
     // Step 5: Symlink .env files from main repo

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jettypod",
-  "version": "4.4.19",
+  "version": "4.4.22",
   "description": "AI-powered development workflow manager with TDD, BDD, and automatic test generation",
   "main": "jettypod.js",
   "bin": {