jettypod 4.1.2 → 4.1.4

package/test-safety-check.sh

@@ -1,80 +0,0 @@
-#!/bin/bash
-
-# Test Safety Verification Script
-# Ensures tests don't modify production files
-
-set -e
-
-echo "🔍 Test Safety Verification Starting..."
-
-# Colors for output
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-# Create snapshots
-echo "📸 Creating production snapshots..."
-if command -v md5sum > /dev/null; then
-  MD5_CMD="md5sum"
-else
-  MD5_CMD="md5 -r"
-fi
-$MD5_CMD package.json > .test-safety-package.md5
-ls -la | grep -v "node_modules" | grep -v ".git" > .test-safety-files.txt
-find . -type f \( -name "*.js" -o -name "*.json" -o -name "*.md" \) | \
-  grep -v node_modules | grep -v .git | \
-  xargs $MD5_CMD > .test-safety-all.md5
-
-# Run tests
-echo "🧪 Running tests..."
-npm test || TEST_FAILED=1
-
-# Verify no changes
-echo "🔍 Verifying production directory..."
-
-# Check package.json
-CURRENT_MD5=$($MD5_CMD package.json)
-ORIGINAL_MD5=$(cat .test-safety-package.md5)
-if [ "$CURRENT_MD5" = "$ORIGINAL_MD5" ]; then
-  echo -e "${GREEN}✓${NC} package.json unchanged"
-else
-  echo -e "${RED}✗${NC} package.json was modified!"
-  SAFETY_FAILED=1
-fi
-
-# Check for leaked files
-LEAKED_FILES=$(ls | grep -E "^(temp_|actual_|main|server|utils|Calculator|helper|app)" || true)
-if [ -z "$LEAKED_FILES" ]; then
-  echo -e "${GREEN}✓${NC} No test artifacts leaked"
-else
-  echo -e "${RED}✗${NC} Test files leaked to production:"
-  echo "$LEAKED_FILES"
-  SAFETY_FAILED=1
-fi
-
-# Check all files
-CURRENT_ALL_MD5=$(find . -type f \( -name "*.js" -o -name "*.json" -o -name "*.md" \) | \
-  grep -v node_modules | grep -v .git | \
-  xargs $MD5_CMD | sort)
-ORIGINAL_ALL_MD5=$(cat .test-safety-all.md5 | sort)
-if [ "$CURRENT_ALL_MD5" = "$ORIGINAL_ALL_MD5" ]; then
-  echo -e "${GREEN}✓${NC} All production files unchanged"
-else
-  echo -e "${YELLOW}⚠${NC} Some files were modified (CLAUDE.md updates are expected)"
-fi
-
-# Cleanup
-rm -f .test-safety-*.md5 .test-safety-*.txt
-
-# Report
-echo ""
-if [ "$SAFETY_FAILED" = "1" ]; then
-  echo -e "${RED}❌ SAFETY CHECK FAILED${NC} - Tests modified production files!"
-  exit 1
-elif [ "$TEST_FAILED" = "1" ]; then
-  echo -e "${YELLOW}⚠️  Tests failed but production is safe${NC}"
-  exit 1
-else
-  echo -e "${GREEN}✅ SAFETY CHECK PASSED${NC} - Production directory is safe!"
-fi

package/work-item-tracking-plan.md

@@ -1,199 +0,0 @@
-# Work Item Tracking Implementation Plan
-
-## Goal
-Keep work items updated throughout feature lifecycle via mode changes and Git hooks.
-
-## Core Components
-
-### 1. Work Item Management
-**Command: `jettypod work start <id>`**
-- Sets work item as "current" (store in `.jettypod/current-work.json`)
-- Auto-updates status `todo` → `in_progress`
-- Creates feature branch: `feature/work-<id>-<slug>`
-- Updates CLAUDE.md `<current_work>` section
-
-**Command: `jettypod work stop`**
-- Clears current work item
-- Prompts for status update before clearing
-
-### 2. Subtask Support
-**Structure: Flat with parent reference**
-```yaml
-- id: 1
-  title: Q1 2025 Goals
-  type: epic
-  status: in_progress
-
-- id: 2
-  title: Work Tracking
-  type: feature
-  parent: 1
-  status: in_progress
-
-- id: 3
-  title: Git hook integration
-  type: task
-  parent: 2
-  status: todo
-```
-
-**Display format:**
-- When starting #3: "Working on: [#3] Git hook integration (subtask of #2 Work Tracking)"
-- In CLAUDE.md: Show full hierarchy chain
-
-### 3. Git Hook Auto-Updates
-
-**Hook: `post-commit`**
-- First commit on feature branch → auto `todo` → `in_progress`
-- Work item already `in_progress` or beyond → skip
-- No current work item → skip silently
-
-**Hook: `prepare-commit-msg`**
-- Committing while status is `todo` → prompt "Work item still 'todo'. Update to 'in_progress'? [Y/n]"
-- Work item is `in_progress` → skip
-- No current work item → skip silently
-
-**Hook: `post-merge`** (or detect merge to main in post-commit)
-- Merged to main → auto → `done`
-- Merged to other branch → skip
-
-### 4. Mode Change Prompts
-
-**Modified: `jettypod mode <mode>`**
-Before switching modes:
-```
-Current work: [#2] Work Tracking (in_progress)
-Update status? [in_progress/blocked/done/skip]: _
-```
-
-- Shows current work item and status
-- Prompts for new status
-- Skip = no change
-- Updates work item + CLAUDE.md before mode change completes
-
-### 5. Hook Installation
-
-**Location:** `.jettypod/hooks/` (templates)
-
-**Setup:**
-- `jettypod init` or first-run setup symlinks to `.git/hooks/`
-- Hooks check for `.jettypod/current-work.json` before doing anything
-- Fail silently if file doesn't exist (not using work tracking yet)
-
-## Work Item Hierarchy
-
-**Epic: [#2] Work Item Lifecycle Automation** (parent: #1 Q1 2025 Goals)
-
-### Features:
-- **[#3] Work item commands** - `jettypod work start/stop`
-- **[#4] Git hook integration** - Auto-update on commits/merges
-- **[#5] Mode change prompts** - Status review on mode switch
-- **[#6] Subtask support** - Parent hierarchy tracking
-
-## Implementation Order
-
-### Feature #3: Work Item Commands (2h max)
-**Type:** feature
-**Parent:** #2 Work Item Lifecycle Automation
-
-1. Write Gherkin scenarios:
-   - Starting work item sets current + creates branch
-   - Starting work item updates status
-   - Stopping work item prompts for status
-   - Subtask display shows parent chain
-   - Integration: starting work updates CLAUDE.md
-
-2. Implement:
-   - `jettypod work start <id>`
-   - `jettypod work stop`
-   - `.jettypod/current-work.json` storage
-   - Parent hierarchy resolution
-   - CLAUDE.md `<current_work>` update
-
-### Feature #4: Git Hook Integration (2h max)
-**Type:** feature
-**Parent:** #2 Work Item Lifecycle Automation
-
-1. Write Gherkin scenarios:
-   - First commit auto-updates to in_progress
-   - Commit while todo prompts for update
-   - Merge to main auto-updates to done
-   - Integration: hooks respect current work item state
-
-2. Implement:
-   - Hook templates in `.jettypod/hooks/`
-   - `post-commit` logic
-   - `prepare-commit-msg` logic
-   - `post-merge` logic
-   - Hook installation in init
-
-### Feature #5: Mode Change Integration (1h max)
-**Type:** feature
-**Parent:** #2 Work Item Lifecycle Automation
-
-1. Write Gherkin scenarios:
-   - Mode change prompts for work item status
-   - Skip option doesn't update
-   - Status update reflects in CLAUDE.md
-   - Integration: mode change + work item update atomic
-
-2. Implement:
-   - Modify `jettypod mode <mode>` to prompt
-   - Update work item from prompt
-   - Update CLAUDE.md
-   - Validate before mode switch completes
-
-### Feature #6: Subtask Support (implicit)
-**Type:** feature
-**Parent:** #2 Work Item Lifecycle Automation
-
-Built into #3 - flat structure with parent references, hierarchy resolution in display logic.
-
-## Edge Cases
-
-### No current work item
-- All hooks skip silently
-- Mode change shows "No active work item"
-
-### Committing directly to main
-- Warn but allow
-- Don't auto-update status (ambiguous)
-
-### Work item already in target status
-- Skip auto-update
-- Don't prompt
-
-### Invalid work item ID in current-work.json
-- Show error
-- Prompt to clear or fix
-
-### Parent work item doesn't exist
-- Show warning
-- Continue (broken reference, but don't block)
-
-## Files Created/Modified
-
-**New:**
-- `.jettypod/hooks/post-commit`
-- `.jettypod/hooks/prepare-commit-msg`
-- `.jettypod/hooks/post-merge`
-- `.jettypod/current-work.json` (generated)
-- `features/work-commands/` (implementation)
-- `features/work-commands/work-commands.feature` (scenarios)
-
-**Modified:**
-- .jettypod.js` (add work start/stop commands)
-- `lib/mode.js` (add status prompt)
-- `lib/init.js` (hook installation)
-- `lib/claudemd.js` (update current_work section)
-
-## Success Criteria
-
-✅ Can start work item and it creates branch + updates CLAUDE.md
-✅ First commit auto-updates status to in_progress
-✅ Committing while todo prompts for update
-✅ Merging to main auto-updates to done
-✅ Mode change prompts for status review
-✅ Subtasks display parent hierarchy
-✅ All Gherkin tests passing (including integration tests)
-✅ Can demo full workflow without manual CLAUDE.md edits