@hienlh/ppm 0.9.81 → 0.9.83

package/.opencode/skills/ck-debug/references/task-management-debugging.md

@@ -1,155 +0,0 @@
-# Debug Task Management Patterns
-
-Track investigation and debugging pipelines via Claude Native Tasks (TaskCreate, TaskUpdate, TaskList).
-
-## When to Create Tasks
-
-| Debug Scope | Tasks? | Rationale |
-|-------------|--------|-----------|
-| Single bug, one file | No | Systematic debugging handles directly |
-| Multi-component investigation (3+ steps) | Yes | Track assess → collect → analyze → fix → verify |
-| Parallel log/data collection agents | Yes | Coordinate independent evidence gathering |
-| Performance investigation with multiple layers | Yes | Track bottleneck analysis per layer |
-| CI/CD pipeline failure with 3+ possible causes | Yes | Track hypothesis elimination |
-
-**3-Task Rule:** Skip task creation when investigation has <3 meaningful steps.
-
-## Investigation Pipeline as Tasks
-
-```
-TaskCreate: "Assess incident scope"      → pending
-TaskCreate: "Collect logs and evidence"  → pending, blockedBy: [assess]
-TaskCreate: "Analyze root cause"         → pending, blockedBy: [collect]
-TaskCreate: "Implement fix"              → pending, blockedBy: [analyze]
-TaskCreate: "Verify fix resolves issue"  → pending, blockedBy: [fix]
-```
-
-Maps to investigation-methodology.md 5-step process. Auto-unblocks as each step completes.
-
-## Task Schemas
-
-### Assess Task
-
-```
-TaskCreate(
-  subject: "Assess {incident} scope and impact",
-  activeForm: "Assessing incident scope",
-  description: "Gather symptoms, identify affected components, check recent changes. See investigation-methodology.md Step 1",
-  metadata: { debugStage: "assess", incident: "{incident}",
-              severity: "P1", effort: "5m" }
-)
-```
-
-### Collect Task
-
-```
-TaskCreate(
-  subject: "Collect evidence for {incident}",
-  activeForm: "Collecting evidence",
-  description: "Server logs, CI/CD logs, database state, metrics. See log-and-ci-analysis.md",
-  metadata: { debugStage: "collect", incident: "{incident}",
-              sources: "logs,ci,db", priority: "P1", effort: "10m" },
-  addBlockedBy: ["{assess-task-id}"]
-)
-```
-
-### Analyze Task
-
-```
-TaskCreate(
-  subject: "Analyze root cause of {incident}",
-  activeForm: "Analyzing root cause",
-  description: "Correlate evidence, trace execution paths, identify root cause. See systematic-debugging.md Phase 1-3",
-  metadata: { debugStage: "analyze", incident: "{incident}",
-              technique: "systematic", priority: "P1", effort: "15m" },
-  addBlockedBy: ["{collect-task-id}"]
-)
-```
-
-### Fix Task
-
-```
-TaskCreate(
-  subject: "Fix root cause: {root_cause_summary}",
-  activeForm: "Implementing fix",
-  description: "Address root cause, add defense-in-depth validation. See defense-in-depth.md",
-  metadata: { debugStage: "fix", rootCause: "{root_cause}",
-              priority: "P1", effort: "20m" },
-  addBlockedBy: ["{analyze-task-id}"]
-)
-```
-
-### Verify Task
-
-```
-TaskCreate(
-  subject: "Verify fix with fresh evidence",
-  activeForm: "Verifying fix",
-  description: "Run tests, check build, confirm issue resolved. NO CLAIMS WITHOUT EVIDENCE. See verification.md",
-  metadata: { debugStage: "verify", priority: "P1", effort: "5m" },
-  addBlockedBy: ["{fix-task-id}"]
-)
-```
-
-## Parallel Evidence Collection
-
-For multi-source investigations, spawn parallel collection agents:
-
-```
-// Parallel — no blockedBy between them
-TaskCreate(subject: "Collect CI/CD pipeline logs",
-  metadata: { debugStage: "collect", source: "ci",
-              agentIndex: 1, totalAgents: 3, priority: "P1" })
-
-TaskCreate(subject: "Collect application server logs",
-  metadata: { debugStage: "collect", source: "server",
-              agentIndex: 2, totalAgents: 3, priority: "P1" })
-
-TaskCreate(subject: "Query database for anomalies",
-  metadata: { debugStage: "collect", source: "db",
-              agentIndex: 3, totalAgents: 3, priority: "P1" })
-
-// Analyze blocks on ALL collection completing:
-TaskCreate(subject: "Analyze root cause from collected evidence",
-  addBlockedBy: ["{ci-id}", "{server-id}", "{db-id}"])
-```
-
-## Task Lifecycle
-
-```
-Assess:   pending → in_progress → completed (scope + impact identified)
-Collect:  pending → in_progress → completed (evidence gathered)
-Analyze:  pending → in_progress → completed (root cause identified)
-Fix:      pending → in_progress → completed (fix implemented)
-Verify:   pending → in_progress → completed (fresh verification evidence)
-```
-
-### Re-Investigation Cycle
-
-When fix doesn't resolve the issue → new analyze-fix-verify cycle:
-
-```
-TaskCreate(subject: "Re-analyze: fix attempt {N} failed",
-  addBlockedBy: ["{verify-task-id}"],
-  metadata: { debugStage: "analyze", cycle: 2, priority: "P1" })
-```
-
-Limit to 3 cycles. After cycle 3 → question architecture (systematic-debugging.md Phase 4.5).
-
-## Integration with Cook/Planning
-
-Debug tasks are **separate from** cook/planning phase tasks.
-
-**When cook spawns debugger:**
-1. Cook encounters failing tests → creates debug pipeline tasks
-2. Debug pipeline executes (assess → collect → analyze → fix → verify)
-3. All debug tasks complete → cook marks phase debugging as done
-4. Cook proceeds to next phase
-
-## Report Sync-Back
-
-After investigation completes, write diagnostic report per reporting-standards.md. Report persists as the "source of truth" for cross-session reference (tasks are session-scoped only).
-
-## Error Handling
-
-If `TaskCreate` fails: log warning, continue with sequential debugging. Tasks add visibility and coordination, not core functionality.

package/.opencode/skills/ck-debug/references/verification.md

@@ -1,123 +0,0 @@
-# Verification Before Completion
-
-Run verification commands and confirm output before claiming success.
-
-## Core Principle
-
-**Evidence before claims, always.**
-
-Claiming work complete without verification is dishonesty, not efficiency.
-
-## The Iron Law
-
-```
-NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
-```
-
-If haven't run verification command in this message, cannot claim it passes.
-
-## The Gate Function
-
-```
-BEFORE claiming any status or expressing satisfaction:
-
-1. IDENTIFY: What command proves this claim?
-2. RUN: Execute FULL command (fresh, complete)
-3. READ: Full output, check exit code, count failures
-4. VERIFY: Does output confirm claim?
-   - If NO: State actual status with evidence
-   - If YES: State claim WITH evidence
-5. ONLY THEN: Make claim
-
-Skip any step = lying, not verifying
-```
-
-## Common Failures
-
-| Claim | Requires | Not Sufficient |
-|-------|----------|----------------|
-| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
-| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
-| Build succeeds | Build command: exit 0 | Linter passing, logs look good |
-| Bug fixed | Test original symptom: passes | Code changed, assumed fixed |
-| Regression test works | Red-green cycle verified | Test passes once |
-| Agent completed | VCS diff shows changes | Agent reports "success" |
-| Requirements met | Line-by-line checklist | Tests passing |
-
-## Red Flags - STOP
-
-- Using "should", "probably", "seems to"
-- Expressing satisfaction before verification ("Great!", "Perfect!", "Done!")
-- About to commit/push/PR without verification
-- Trusting agent success reports
-- Relying on partial verification
-- Thinking "just this once"
-- Tired and wanting work over
-- **ANY wording implying success without having run verification**
-
-## Rationalization Prevention
-
-| Excuse | Reality |
-|--------|---------|
-| "Should work now" | RUN verification |
-| "I'm confident" | Confidence ≠ evidence |
-| "Just this once" | No exceptions |
-| "Linter passed" | Linter ≠ compiler |
-| "Agent said success" | Verify independently |
-| "Partial check is enough" | Partial proves nothing |
-
-## Key Patterns
-
-**Tests:**
-```
-✅ [Run test command] [See: 34/34 pass] "All tests pass"
-❌ "Should pass now" / "Looks correct"
-```
-
-**Regression tests (TDD Red-Green):**
-```
-✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
-❌ "I've written regression test" (without red-green verification)
-```
-
-**Build:**
-```
-✅ [Run build] [See: exit 0] "Build passes"
-❌ "Linter passed" (linter doesn't check compilation)
-```
-
-**Requirements:**
-```
-✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
-❌ "Tests pass, phase complete"
-```
-
-**Agent delegation:**
-```
-✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
-❌ Trust agent report
-```
-
-## When To Apply
-
-**ALWAYS before:**
-- ANY variation of success/completion claims
-- ANY expression of satisfaction
-- ANY positive statement about work state
-- Committing, PR creation, task completion
-- Moving to next task
-- Delegating to agents
-
-**Rule applies to:**
-- Exact phrases
-- Paraphrases and synonyms
-- Implications of success
-- ANY communication suggesting completion/correctness
-
-## The Bottom Line
-
-**No shortcuts for verification.**
-
-Run command. Read output. THEN claim result.
-
-Non-negotiable.

package/.opencode/skills/ck-debug/scripts/find-polluter.sh

@@ -1,63 +0,0 @@
-#!/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/.opencode/skills/ck-debug/scripts/find-polluter.test.md

@@ -1,102 +0,0 @@
-# find-polluter.sh Test Documentation
-
-## Purpose
-Bisection script to find which test creates unwanted files or state pollution.
-
-## Manual Test Procedure
-
-### Setup Test Scenario
-```bash
-# Create test directory
-mkdir -p /tmp/polluter-test && cd /tmp/polluter-test
-
-# Create clean test
-cat > test1.test.js << 'EOF'
-console.log('Test 1: clean');
-EOF
-
-# Create polluter test
-cat > test2.test.js << 'EOF'
-const fs = require('fs');
-fs.mkdirSync('.git', { recursive: true });
-console.log('Test 2: creates pollution');
-EOF
-
-# Create another clean test
-cat > test3.test.js << 'EOF'
-console.log('Test 3: clean');
-EOF
-```
-
-### Run Script
-```bash
-# For projects with npm test
-/path/to/find-polluter.sh '.git' 'src/**/*.test.ts'
-
-# For node-only tests (modify script to use 'node' instead of 'npm test')
-./find-polluter.sh '.git' '*.test.js'
-```
-
-### Expected Output
-```
-🔍 Searching for test that creates: .git
-Test pattern: *.test.js
-
-Found 3 test files
-
-[1/3] Testing: ./test1.test.js
-[2/3] Testing: ./test2.test.js
-
-🎯 FOUND POLLUTER!
-   Test: ./test2.test.js
-   Created: .git
-```
-
-### Cleanup
-```bash
-rm -rf /tmp/polluter-test
-```
-
-## Test Results
-
-✅ Script logic verified (2025-11-11)
-- Correctly iterates through test files
-- Detects pollution creation
-- Reports the polluting test file
-- Exits early when polluter found
-
-## Usage Notes
-
-**Prerequisites:**
-- Test runner (npm test) must be configured in project
-- Test pattern must match actual test files
-- Pollution path must be accurate
-
-**Customization:**
-If your project doesn't use `npm test`, modify line 42:
-```bash
-# Replace
-npm test "$TEST_FILE" > /dev/null 2>&1 || true
-
-# With your test command
-node "$TEST_FILE" > /dev/null 2>&1 || true
-# Or
-jest "$TEST_FILE" > /dev/null 2>&1 || true
-```
-
-## Common Use Cases
-
-1. **Find test creating .git directory:**
-   ```bash
-   ./find-polluter.sh '.git' 'src/**/*.test.ts'
-   ```
-
-2. **Find test creating node_modules:**
-   ```bash
-   ./find-polluter.sh 'node_modules' 'test/**/*.spec.js'
-   ```
-
-3. **Find test creating specific file:**
-   ```bash
-   ./find-polluter.sh 'unwanted-file.txt' '**/*.test.js'
-   ```

package/.opencode/skills/ck-loop/SKILL.md

@@ -1,149 +0,0 @@
----
-name: ck:loop
-description: "Autonomous iterative optimization loop — run N iterations against a mechanical metric, learn from git history, auto-keep/discard changes. Use for improving measurable metrics (coverage, performance, bundle size, etc.) through repeated experimentation."
-argument-hint: "[Goal/Metric description] or inline config block"
-metadata:
-  author: claudekit
-  attribution: "Core patterns adapted from autoresearch by Udit Goenka (MIT)"
-  license: MIT
-  version: "1.0.0"
----
-
-# ck:loop — Autonomous Optimization Loop
-
-> Constraint + Mechanical Metric + Fast Verification = Autonomous Improvement
-
-## When to Use
-
-- Improve a measurable metric (test coverage, bundle size, ESLint errors, Lighthouse score, etc.)
-- Autonomous execution over N iterations without manual intervention
-- Git-tracked experiments where you want rollback on regression
-- Exploring a search space of code changes with consistent evaluation
-
-## When NOT to Use
-
-| Situation | Better Tool |
-|-----------|-------------|
-| Subjective goals ("make it cleaner") | `ck:cook` |
-| Bug fixing with known root cause | `ck:fix` or `ck:debug` |
-| One-shot tasks, no repetition needed | `ck:cook` |
-| No mechanical metric to measure progress | `ck:cook --interactive` |
-| Files outside a defined scope | manual approach |
-
-## Configuration Format
-
-Parsed from user message. Missing required fields trigger a **batched** `AskUserQuestion`.
-
-### Required
-
-| Field | Description | Example |
-|-------|-------------|---------|
-| `Goal` | Human description of what to improve | `"Increase test coverage in src/utils"` |
-| `Scope` | Glob pattern(s) for editable files | `"src/utils/**/*.ts"` |
-| `Verify` | Shell command that outputs **a single number** | `"npx jest --coverage --json \| jq '.coverageMap \| .. \| .s? \| to_entries \| map(.value) \| (map(select(.>0)) \| length) / length * 100' \| tail -1"` |
-
-### Optional
-
-| Field | Default | Description |
-|-------|---------|-------------|
-| `Guard` | none | Regression check command (exit 0 = pass) |
-| `Iterations` | 10 | Maximum iterations to run |
-| `Noise` | medium | Tolerance for metric variance: `low` / `medium` / `high` |
-| `Min-Delta` | 0 | Minimum improvement to count as progress |
-| `Direction` | higher | Whether `higher` or `lower` metric value is better |
-
-## Interactive Setup
-
-When required fields are missing, ask all at once:
-
-```
-AskUserQuestion({
-  questions: [
-    { question: "What metric do you want to improve? (e.g. 'test coverage in src/utils')", field: "Goal" },
-    { question: "Which files may be edited? (glob, e.g. 'src/utils/**/*.ts')", field: "Scope" },
-    { question: "Verify command — must print a single number to stdout", field: "Verify" },
-    { question: "Guard command for regression check? (optional, press Enter to skip)", field: "Guard" }
-  ]
-})
-```
-
-## Core Protocol
-
-See [`references/autonomous-loop-protocol.md`](references/autonomous-loop-protocol.md) for the full 8-phase specification.
-
-**Key invariants:**
-- ONE atomic change per iteration — atomicity test: can you describe it in one sentence without "and"?
-- Commit BEFORE verify — git is memory, not a safety net
-- Guard files are **read-only** — never modify files in guard command's scope
-- Prefer `git revert` over `git reset` — preserve history
-
-## Results Logging
-
-Each iteration appends a TSV line to `loop-results.tsv` in the working directory:
-
-```
-iter  timestamp           metric  delta   kept  description
-1     2026-03-27T13:50:00 82.4    +2.4    yes   add null checks to parser.ts
-2     2026-03-27T13:51:10 81.9    -0.5    no    extract helper function
-```
-
-See [`references/autonomous-loop-protocol.md`](references/autonomous-loop-protocol.md) — Phase 7 for full schema.
-
-## Stuck Detection
-
-| Condition | Action |
-|-----------|--------|
-| 5 consecutive discards | Analyze patterns → shift strategy (different files, different approach) |
-| 10 consecutive discards | STOP — report findings, surface to user |
-
-## Example Invocations
-
-### 1. Increase test coverage
-
-```
-/ck:loop
-Goal: Increase test coverage in src/utils from ~60% to 80%
-Scope: src/utils/**/*.ts, tests/utils/**/*.test.ts
-Verify: npx jest tests/utils --coverage --coverageReporters=json-summary 2>/dev/null | node -e "const d=require('./coverage-summary.json');console.log(d.total.lines.pct)"
-Guard: npx tsc --noEmit && npx jest --passWithNoTests
-Iterations: 15
-Direction: higher
-```
-
-### 2. Reduce bundle size
-
-```
-/ck:loop
-Goal: Reduce main bundle size below 200KB
-Scope: src/**/*.ts, src/**/*.tsx
-Verify: npx vite build 2>/dev/null | grep "dist/index" | awk '{print $2}' | sed 's/kB//'
-Guard: npx tsc --noEmit
-Direction: lower
-Min-Delta: 0.5
-```
-
-### 3. Eliminate ESLint errors
-
-```
-/ck:loop
-Goal: Drive ESLint error count to zero in src/api
-Scope: src/api/**/*.ts
-Verify: npx eslint src/api --format=json 2>/dev/null | node -e "const r=require('/dev/stdin');console.log(r.reduce((a,f)=>a+f.errorCount,0))" || echo 999
-Direction: lower
-Iterations: 20
-```
-
-## Limitations (Honest)
-
-- Cannot optimize subjective or aesthetic goals
-- Cannot modify files outside the declared `Scope`
-- Cannot modify files referenced by the `Guard` command
-- Cannot guarantee improvement — some metrics have hard ceilings
-- Requires a **git repository with a clean working tree** before starting
-- `Verify` command must complete in **< 30 seconds** (otherwise loop is impractical)
-- Does not parallelize iterations — sequential by design (each iteration learns from the last)
-
-## References
-
-- [`references/autonomous-loop-protocol.md`](references/autonomous-loop-protocol.md) — Full 8-phase loop spec, decision matrix, anti-patterns
-- [`references/git-memory-pattern.md`](references/git-memory-pattern.md) — Git as cross-iteration memory, revert vs reset, commit conventions