liteagents 2.4.0

package/packages/droid/commands/docs-builder.md

@@ -0,0 +1,106 @@
+---
+name: docs-builder
+description: Create comprehensive project documentation with structured /docs hierarchy
+usage: /docs-builder
+auto_trigger: false
+---
+
+# Documentation Architecture Skill
+
+Create systematic /docs structure following this 5-tier hierarchy:
+
+```
+/docs
+├── 00-context/              # WHY and WHAT EXISTS RIGHT NOW
+├── 01-product/              # WHAT the product must do
+├── 02-features/             # HOW features are designed & built
+├── 03-logs/                 # MEMORY (what changed over time)
+├── 04-process/              # HOW to work with this system
+└── README.md                # Navigation guide
+```
+
+## Workflow
+
+### 1. Discover Project
+- Scan: README, existing /docs, package.json/pyproject.toml, src/, tests/
+- Map existing docs: commands/ → where? development/ → where?
+- Ask: "What's built? What's planned? What's missing?"
+
+### 2. Create Directories
+```bash
+mkdir -p docs/{00-context,01-product,02-features,03-logs,04-process}
+```
+
+### 3. Create Files with TodoWrite
+
+Track progress:
+- [ ] 00-context (3 files: vision.md, assumptions.md, system-state.md)
+- [ ] 01-product (1 file: prd.md)
+- [ ] 02-features (per feature discovered: feature-spec.md, tech-design.md, dev-tasks.md, test-plan.md)
+- [ ] 03-logs (5 files: implementation-log.md, decisions-log.md, bug-log.md, validation-log.md, insights.md)
+- [ ] 04-process (3 files: dev-workflow.md, definition-of-done.md, llm-prompts.md)
+- [ ] docs/README.md
+
+Mark each **completed** before next.
+
+For detailed templates, see: `docs-builder/templates.md`
+
+### 4. Integrate with Existing Docs
+
+**If CLAUDE.md/KNOWLEDGE_BASE.md exist**:
+Update KNOWLEDGE_BASE.md to reference new structure:
+```markdown
+## Project Documentation
+Full /docs structure with context, product, features, logs, process
+→ `docs/README.md`
+```
+
+**If existing /docs subdirs exist**:
+- Don't delete - add migration note in docs/README.md
+- Reference existing content where relevant
+- Note in system-state.md that migration in progress
+
+### 5. Validate
+
+```bash
+# Check structure
+ls -la docs/{00-context,01-product,02-features,03-logs,04-process}
+
+# Count minimum files
+find docs/00-context -name "*.md" | wc -l  # >= 3
+find docs/03-logs -name "*.md" | wc -l     # >= 5
+find docs/04-process -name "*.md" | wc -l  # >= 3
+test -f docs/01-product/prd.md && echo "✓ PRD exists"
+test -f docs/README.md && echo "✓ README exists"
+```
+
+## Rules
+
+**DO**:
+- Complete one section fully before next
+- Use TodoWrite to track progress
+- Populate files (don't leave empty templates)
+- Use discovered content from project
+- Create feature-<name>/ for each major feature found
+- Initialize all 5 log files with format
+- Mark todos completed immediately after finishing
+
+**DON'T**:
+- Skip sections
+- Create empty placeholders
+- Duplicate content across files
+- Delete existing docs
+- Forget to validate at end
+
+## Success Criteria
+
+✅ All 5 tier directories created
+✅ Minimum files in each (00-context: 3, 01-product: 1, 03-logs: 5, 04-process: 3)
+✅ Files populated with project-specific content
+✅ Feature folders created for discovered features
+✅ docs/README.md complete with navigation
+✅ Integration with CLAUDE.md/KNOWLEDGE_BASE.md done
+✅ Validation checks pass
+✅ All todos marked completed
+
+Complete when /docs structure is fully populated and navigable.

package/packages/droid/commands/explain.md

@@ -0,0 +1,18 @@
+---
+name: explain
+description: Explain [code]
+usage: /explain <code-section>
+argument-hint: [file, function, or concept]
+model: claude-3-5-haiku-20241022
+---
+Explain $ARGUMENTS.
+
+## Cover
+- What it does (purpose)
+- How it works (step by step)
+- Why it's designed this way
+- Dependencies and side effects
+- Potential gotchas
+
+Assume reader knows the language but not this codebase.
+

package/packages/droid/commands/git-commit.md

@@ -0,0 +1,14 @@
+---
+name: git-commit
+description: Analyze changes and commit
+usage: /git-commit
+allowed-tools: Bash(git *)
+---
+1. Run `git diff --staged` to see changes
+2. Analyze what was changed and why
+3. Create a commit message:
+   - Format: type(scope): description
+   - Types: feat, fix, refactor, docs, test, chore
+   - Under 72 chars
+   - Body explains WHY if non-obvious
+4. Execute the commit

package/packages/droid/commands/optimize.md

@@ -0,0 +1,20 @@
+---
+name: optimize
+description: Optimize performance [target]
+usage: /optimize <target-area>
+argument-hint: [file-or-function]
+---
+Analyze $ARGUMENTS for performance.
+
+## Examine
+- Time complexity (Big O)
+- Space complexity
+- I/O operations
+- Database queries (N+1?)
+- Unnecessary allocations
+
+## Output
+- Current bottlenecks
+- Specific optimizations
+- Expected improvement
+- Trade-offs involved

package/packages/droid/commands/refactor.md

@@ -0,0 +1,21 @@
+---
+name: refactor
+description: Refactor [code]
+usage: /refactor <code-section>
+argument-hint: [file-or-function]
+---
+Refactor $ARGUMENTS.
+
+## Goals
+- Reduce complexity
+- Improve readability
+- Apply DRY
+- Better naming
+- Smaller functions (single responsibility)
+
+## Constraints
+- NO behavior changes
+- Keep public API intact
+- Existing tests must pass
+
+Explain each change.

package/packages/droid/commands/review.md

@@ -0,0 +1,18 @@
+---
+name: review
+description: Review code [file]
+usage: /review
+argument-hint: [file or leave empty for staged changes]
+---
+Review $ARGUMENTS (or staged changes if not specified).
+
+## Check For
+- Security: OWASP Top 10, auth issues, data exposure
+- Performance: N+1 queries, memory leaks, blocking calls
+- Correctness: Edge cases, error handling, type safety
+- Maintainability: Complexity, naming, duplication
+
+## Output Format
+### 🚨 Critical (blocks merge)
+### ⚠️ Warnings (should fix)
+### 💡 Suggestions (nice to have)

package/packages/droid/commands/root-cause-tracing/find-polluter.sh

@@ -0,0 +1,63 @@
+#!/bin/bash
+# Bisection script to find which test creates unwanted files/state
+# Usage: ./find-polluter.sh <file_or_dir_to_check> <test_pattern>
+# Example: ./find-polluter.sh '.git' 'src/**/*.test.ts'
+
+set -e
+
+if [ $# -ne 2 ]; then
+  echo "Usage: $0 <file_to_check> <test_pattern>"
+  echo "Example: $0 '.git' 'src/**/*.test.ts'"
+  exit 1
+fi
+
+POLLUTION_CHECK="$1"
+TEST_PATTERN="$2"
+
+echo "🔍 Searching for test that creates: $POLLUTION_CHECK"
+echo "Test pattern: $TEST_PATTERN"
+echo ""
+
+# Get list of test files
+TEST_FILES=$(find . -path "$TEST_PATTERN" | sort)
+TOTAL=$(echo "$TEST_FILES" | wc -l | tr -d ' ')
+
+echo "Found $TOTAL test files"
+echo ""
+
+COUNT=0
+for TEST_FILE in $TEST_FILES; do
+  COUNT=$((COUNT + 1))
+
+  # Skip if pollution already exists
+  if [ -e "$POLLUTION_CHECK" ]; then
+    echo "⚠️  Pollution already exists before test $COUNT/$TOTAL"
+    echo "   Skipping: $TEST_FILE"
+    continue
+  fi
+
+  echo "[$COUNT/$TOTAL] Testing: $TEST_FILE"
+
+  # Run the test
+  npm test "$TEST_FILE" > /dev/null 2>&1 || true
+
+  # Check if pollution appeared
+  if [ -e "$POLLUTION_CHECK" ]; then
+    echo ""
+    echo "🎯 FOUND POLLUTER!"
+    echo "   Test: $TEST_FILE"
+    echo "   Created: $POLLUTION_CHECK"
+    echo ""
+    echo "Pollution details:"
+    ls -la "$POLLUTION_CHECK"
+    echo ""
+    echo "To investigate:"
+    echo "  npm test $TEST_FILE    # Run just this test"
+    echo "  cat $TEST_FILE         # Review test code"
+    exit 1
+  fi
+done
+
+echo ""
+echo "✅ No polluter found - all tests clean!"
+exit 0

package/packages/droid/commands/root-cause-tracing.md

@@ -0,0 +1,176 @@
+---
+name: root-cause-tracing
+description: Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
+usage: /root-cause-tracing <issue-description>
+auto_trigger: false
+---
+
+# Root Cause Tracing
+
+## Overview
+
+Bugs often manifest deep in the call stack (git init in wrong directory, file created in wrong location, database opened with wrong path). Your instinct is to fix where the error appears, but that's treating a symptom.
+
+**Core principle:** Trace backward through the call chain until you find the original trigger, then fix at the source.
+
+## When to Use
+
+```dot
+digraph when_to_use {
+    "Bug appears deep in stack?" [shape=diamond];
+    "Can trace backwards?" [shape=diamond];
+    "Fix at symptom point" [shape=box];
+    "Trace to original trigger" [shape=box];
+    "BETTER: Also add defense-in-depth" [shape=box];
+
+    "Bug appears deep in stack?" -> "Can trace backwards?" [label="yes"];
+    "Can trace backwards?" -> "Trace to original trigger" [label="yes"];
+    "Can trace backwards?" -> "Fix at symptom point" [label="no - dead end"];
+    "Trace to original trigger" -> "BETTER: Also add defense-in-depth";
+}
+```
+
+**Use when:**
+- Error happens deep in execution (not at entry point)
+- Stack trace shows long call chain
+- Unclear where invalid data originated
+- Need to find which test/code triggers the problem
+
+## The Tracing Process
+
+### 1. Observe the Symptom
+```
+Error: git init failed in /Users/jesse/project/packages/core
+```
+
+### 2. Find Immediate Cause
+**What code directly causes this?**
+```typescript
+await execFileAsync('git', ['init'], { cwd: projectDir });
+```
+
+### 3. Ask: What Called This?
+```typescript
+WorktreeManager.createSessionWorktree(projectDir, sessionId)
+  → called by Session.initializeWorkspace()
+  → called by Session.create()
+  → called by test at Project.create()
+```
+
+### 4. Keep Tracing Up
+**What value was passed?**
+- `projectDir = ''` (empty string!)
+- Empty string as `cwd` resolves to `process.cwd()`
+- That's the source code directory!
+
+### 5. Find Original Trigger
+**Where did empty string come from?**
+```typescript
+const context = setupCoreTest(); // Returns { tempDir: '' }
+Project.create('name', context.tempDir); // Accessed before beforeEach!
+```
+
+## Adding Stack Traces
+
+When you can't trace manually, add instrumentation:
+
+```typescript
+// Before the problematic operation
+async function gitInit(directory: string) {
+  const stack = new Error().stack;
+  console.error('DEBUG git init:', {
+    directory,
+    cwd: process.cwd(),
+    nodeEnv: process.env.NODE_ENV,
+    stack,
+  });
+
+  await execFileAsync('git', ['init'], { cwd: directory });
+}
+```
+
+**Critical:** Use `console.error()` in tests (not logger - may not show)
+
+**Run and capture:**
+```bash
+npm test 2>&1 | grep 'DEBUG git init'
+```
+
+**Analyze stack traces:**
+- Look for test file names
+- Find the line number triggering the call
+- Identify the pattern (same test? same parameter?)
+
+## Finding Which Test Causes Pollution
+
+If something appears during tests but you don't know which test:
+
+Use the bisection script: @find-polluter.sh
+
+```bash
+./find-polluter.sh '.git' 'src/**/*.test.ts'
+```
+
+Runs tests one-by-one, stops at first polluter. See script for usage.
+
+## Real Example: Empty projectDir
+
+**Symptom:** `.git` created in `packages/core/` (source code)
+
+**Trace chain:**
+1. `git init` runs in `process.cwd()` ← empty cwd parameter
+2. WorktreeManager called with empty projectDir
+3. Session.create() passed empty string
+4. Test accessed `context.tempDir` before beforeEach
+5. setupCoreTest() returns `{ tempDir: '' }` initially
+
+**Root cause:** Top-level variable initialization accessing empty value
+
+**Fix:** Made tempDir a getter that throws if accessed before beforeEach
+
+**Also added defense-in-depth:**
+- Layer 1: Project.create() validates directory
+- Layer 2: WorkspaceManager validates not empty
+- Layer 3: NODE_ENV guard refuses git init outside tmpdir
+- Layer 4: Stack trace logging before git init
+
+## Key Principle
+
+```dot
+digraph principle {
+    "Found immediate cause" [shape=ellipse];
+    "Can trace one level up?" [shape=diamond];
+    "Trace backwards" [shape=box];
+    "Is this the source?" [shape=diamond];
+    "Fix at source" [shape=box];
+    "Add validation at each layer" [shape=box];
+    "Bug impossible" [shape=doublecircle];
+    "NEVER fix just the symptom" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
+
+    "Found immediate cause" -> "Can trace one level up?";
+    "Can trace one level up?" -> "Trace backwards" [label="yes"];
+    "Can trace one level up?" -> "NEVER fix just the symptom" [label="no"];
+    "Trace backwards" -> "Is this the source?";
+    "Is this the source?" -> "Trace backwards" [label="no - keeps going"];
+    "Is this the source?" -> "Fix at source" [label="yes"];
+    "Fix at source" -> "Add validation at each layer";
+    "Add validation at each layer" -> "Bug impossible";
+}
+```
+
+**NEVER fix just where the error appears.** Trace back to find the original trigger.
+
+## Stack Trace Tips
+
+**In tests:** Use `console.error()` not logger - logger may be suppressed
+**Before operation:** Log before the dangerous operation, not after it fails
+**Include context:** Directory, cwd, environment variables, timestamps
+**Capture stack:** `new Error().stack` shows complete call chain
+
+## Real-World Impact
+
+From debugging session (2025-10-03):
+- Found root cause through 5-level trace
+- Fixed at source (getter validation)
+- Added 4 layers of defense
+- 1847 tests passed, zero pollution

package/packages/droid/commands/security.md

@@ -0,0 +1,21 @@
+---
+name: security
+description: Scan security [target]
+usage: /security
+argument-hint: [file, directory, or leave empty for full scan]
+allowed-tools: Read, Grep, Glob
+---
+Audit $ARGUMENTS for security vulnerabilities.
+
+## Check For
+- Injection: SQL, command, XSS, template
+- Auth: Weak passwords, session issues, CSRF
+- Data: Exposure, logging secrets, insecure storage
+- Config: Debug mode, default creds, missing headers
+- Dependencies: Known CVEs
+
+## Output
+Severity-ranked findings with:
+- Location (file:line)
+- Risk explanation
+- Remediation steps

package/packages/droid/commands/ship.md

@@ -0,0 +1,18 @@
+---
+name: ship
+description: Check pre-deployment
+usage: /ship
+allowed-tools: Bash(npm *), Bash(git *)
+---
+Pre-deploy checklist:
+
+- [ ] Tests pass (`npm test`)
+- [ ] Lint clean (`npm run lint`)
+- [ ] Build succeeds (`npm run build`)
+- [ ] No console.log/debugger statements
+- [ ] Env vars documented
+- [ ] No hardcoded secrets
+- [ ] Error handling complete
+- [ ] Migrations ready
+
+Run checks and report: Ready 🚀 or Blocked 🛑 with issues.