jettypod 4.4.46 → 4.4.47

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "jettypod",
3
- "version": "4.4.46",
3
+ "version": "4.4.47",
4
4
  "description": "AI-powered development workflow manager with TDD, BDD, and automatic test generation",
5
5
  "main": "jettypod.js",
6
6
  "bin": {
@@ -78,6 +78,14 @@ Implementation Plan:
78
78
 
79
79
  **Your task:** Create an isolated worktree for this chore.
80
80
 
81
+ **🚫 FORBIDDEN: Manual Git Worktree Commands**
82
+ ```
83
+ ❌ git worktree add ...
84
+ ❌ git checkout -b feature/...
85
+ ❌ git branch feature/...
86
+ ```
87
+ **ALWAYS use `jettypod work start`** - it handles branch naming, path conventions, database tracking, and cleanup. Manual git commands will create orphaned worktrees that break the merge workflow.
88
+
81
89
  ```bash
82
90
  jettypod work start [chore-id]
83
91
  ```
@@ -588,6 +588,14 @@ Now I'll write the BDD tests in an isolated worktree...
588
588
 
589
589
  **CRITICAL:** Tests are written in an isolated worktree, not directly on main. This ensures agent failures don't leave uncommitted garbage on main.
590
590
 
591
+ **🚫 FORBIDDEN: Manual Git Worktree Commands**
592
+ ```
593
+ ❌ git worktree add ...
594
+ ❌ git checkout -b tests/...
595
+ ❌ git branch tests/...
596
+ ```
597
+ **ALWAYS use jettypod commands** - they handle branch naming, path conventions, database tracking, and cleanup. Manual git commands will create orphaned worktrees that break the merge workflow.
598
+
591
599
  **Sub-step 1: Create test worktree**
592
600
 
593
601
  ```bash
@@ -756,6 +764,14 @@ End feature-planning skill without starting a chore. Do NOT invoke speed-mode.
756
764
 
757
765
  **After user picks a chore, execute these steps IN ORDER:**
758
766
 
767
+ **🚫 FORBIDDEN: Manual Git Worktree Commands**
768
+ ```
769
+ ❌ git worktree add ...
770
+ ❌ git checkout -b feature/...
771
+ ❌ git branch feature/...
772
+ ```
773
+ **ALWAYS use `jettypod work start`** - it handles branch naming, path conventions, database tracking, and cleanup. Manual git commands will create orphaned worktrees that break the merge workflow.
774
+
759
775
  **Step 1: Start the chore (creates worktree and branch):**
760
776
  ```bash
761
777
  jettypod work start [chore-id]
@@ -629,6 +629,14 @@ After merge, you are on main branch. Ready to generate stable mode scenarios.
629
629
 
630
630
  **1. Create a test worktree for writing stable mode scenarios:**
631
631
 
632
+ **🚫 FORBIDDEN: Manual Git Worktree Commands**
633
+ ```
634
+ ❌ git worktree add ...
635
+ ❌ git checkout -b tests/...
636
+ ❌ git branch tests/...
637
+ ```
638
+ **ALWAYS use jettypod commands** - they handle branch naming, path conventions, database tracking, and cleanup. Manual git commands will create orphaned worktrees that break the merge workflow.
639
+
632
640
  ```bash
633
641
  jettypod work tests <feature-id>
634
642
  ```
@@ -72,6 +72,14 @@ sqlite3 .jettypod/work.db "SELECT wi.id, wi.title, wi.status, wt.worktree_path,
72
72
 
73
73
  **🛑 STOP GATE:** If `worktree_path` is NULL or no rows returned, you MUST run `jettypod work start [chore-id]` before continuing. DO NOT proceed without a valid worktree.
74
74
 
75
+ **🚫 FORBIDDEN: Manual Git Worktree Commands**
76
+ ```
77
+ ❌ git worktree add ...
78
+ ❌ git checkout -b feature/...
79
+ ❌ git branch feature/...
80
+ ```
81
+ **ALWAYS use `jettypod work start`** - it handles branch naming, path conventions, database tracking, and cleanup. Manual git commands will create orphaned worktrees that break the merge workflow.
82
+
75
83
  **Example of valid output:**
76
84
  ```
77
85
  4|Add error handling|in_progress|/Users/erik/project/.jettypod-work/4-add-error-handling|feature/work-4-add-error-handling