claude-code-pilot 2.0.0 → 3.1.0

package/{kit/commands → src/commands/ccp}/setup-refresh.md

@@ -1,4 +1,5 @@
 ---
+name: ccp:setup-refresh
 description: "Re-scan codebase and update CLAUDE.md, rules, directory CLAUDE.md files, and architecture docs after major changes"
 ---
 
@@ -23,10 +24,10 @@ Present differences.
    - Scan for recognized directories: `src/`, `test/`, `tests/`, `lib/`, `app/`, `api/`, `scripts/`, `docs/`
    - For each existing recognized directory with a CLAUDE.md file:
      - Read the file's first line
-     - If it contains `<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->`: regenerate using the same stack-aware templates from /setup Stage 4
+     - If it contains `<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->`: regenerate using the same stack-aware templates from /ccp:setup Stage 4
      - If the marker is absent: skip (print: "Skipping {dir}/CLAUDE.md -- customized by user")
    - For each recognized directory WITHOUT a CLAUDE.md file:
-     - Generate a new one using the same stack-aware templates from /setup Stage 4
+     - Generate a new one using the same stack-aware templates from /ccp:setup Stage 4
    - Show summary of changes:
      ```
      Directory CLAUDE.md refresh:
@@ -40,7 +41,7 @@ Present differences.
 
 Show diff before writing.
 
-Note: MCP detection is NOT re-run during refresh. Binaries rarely change. Re-run `/setup` to re-detect MCP tools.
+Note: MCP detection is NOT re-run during refresh. Binaries rarely change. Re-run `/ccp:setup` to re-detect MCP tools.
 
 ## Step 3 — Commit
 

package/{kit/commands → src/commands/ccp}/setup.md

@@ -1,4 +1,5 @@
 ---
+name: ccp:setup
 description: "First-time project setup — scans codebase, generates CLAUDE.md, installs language rules, discovers skills"
 ---
 
@@ -12,10 +13,10 @@ Verify that all 4 source directories from the Claude Code Pilot are properly ins
 
 Check the following paths relative to the project root:
 
-1. **Kit commands** — check if `.claude/commands/setup.md` exists (this file is a kit-specific marker)
-2. **GSD commands** — check if `.claude/commands/gsd/` directory exists and is non-empty (contains the 32 GSD commands)
-3. **ECC toolbox** — check if `.claude/ecc-scripts/` directory exists (contains hooks, lib, detection scripts)
-4. **GSD SDLC workflows** — check if `.claude/get-shit-done/` directory exists and contains `workflows/` subdirectory
+1. **Kit commands** — check if `.claude/commands/ccp/setup.md` exists (this file is a kit-specific marker)
+2. **CCP commands** — check if `.claude/commands/ccp/` directory exists and is non-empty (contains the 32 CCP commands)
+3. **CCP toolbox** — check if `.claude/hooks/` directory exists (contains hooks, lib, detection scripts)
+4. **CCP SDLC workflows** — check if `.claude/pilot/` directory exists and contains `workflows/` subdirectory
 
 Use the Bash tool to run existence checks (e.g., `ls` or `test -d`). Count items in each directory.
 
@@ -23,17 +24,17 @@ Present results in this format:
 ```
 Source Directory Detection:
   [PASS] Kit commands     .claude/commands/ (N kit commands)
-  [PASS] GSD commands     .claude/commands/gsd/ (N commands)
-  [PASS] ECC toolbox      .claude/ecc-scripts/ (hooks, lib, detection)
-  [PASS] GSD workflows    .claude/get-shit-done/ (workflows, references, templates)
+  [PASS] CCP commands     .claude/commands/ccp/ (N commands)
+  [PASS] CCP toolbox      .claude/hooks/ (hooks, lib, detection)
+  [PASS] CCP workflows    .claude/pilot/ (workflows, references, templates)
 
 All 4 source directories detected.
 ```
 
 If any directory is missing, show:
 ```
-  [FAIL] GSD commands     .claude/commands/gsd/ -- NOT FOUND
-         Fix: Run /kit:update or reinstall with npx claude-code-pilot@latest
+  [FAIL] CCP commands     .claude/commands/ccp/ -- NOT FOUND
+         Fix: Run /ccp:update or reinstall with npx claude-code-pilot@latest
 ```
 
 Continue to Stage 1 regardless — detection is informational, not blocking.
@@ -53,6 +54,32 @@ Check if this is an existing codebase or new project:
 
 ## Stage 2A — Scan Existing Codebase
 
+### Codebase Intelligence Check
+
+Before subagent exploration, check if codebase-memory-mcp is available for richer codebase analysis:
+
+1. Read `.mcp.json` from project root
+2. Check if `mcpServers["codebase-memory-mcp"]` key exists
+3. If YES: attempt to use the `search_graph` MCP tool to get high-level codebase information:
+   - Call `search_graph` with query: "project structure and main components"
+   - If the call succeeds and returns data: use it to supplement the subagent exploration below (skip redundant grep/find for items already covered by graph results)
+   - If the call fails or returns empty: log a warning and continue with standard exploration
+
+```
+Codebase Intelligence:
+  [ACTIVE]  codebase-memory-mcp detected in .mcp.json — using graph queries for richer analysis
+  -- or --
+  [FALLBACK] codebase-memory-mcp not configured — using file exploration
+  -- or --
+  [FALLBACK] codebase-memory-mcp not responding — falling back to file exploration
+```
+
+4. If NO (key not in .mcp.json): skip graph queries entirely, proceed with standard subagent exploration below.
+
+**Important:** This is a best-effort enhancement. The standard subagent exploration (grep/find) must ALWAYS run as the baseline. Graph results supplement, they don't replace. If codebase-memory-mcp adds value, great. If not, /ccp:setup works exactly as before.
+
+---
+
 Use subagents to explore (keeps main context clean). Tailor the exploration prompts based on what Stage 1 detected:
 
 **If Next.js detected** (react + next in dependencies, or next.config.* exists):
@@ -159,7 +186,7 @@ Skip any directory that does not exist.
 
 For each existing recognized directory:
 - If no `CLAUDE.md` exists in the directory: mark for generation
-- If `CLAUDE.md` exists and its **first line** contains `<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->`: mark for regeneration (overwrite)
+- If `CLAUDE.md` exists and its **first line** contains `<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->`: mark for regeneration (overwrite)
 - If `CLAUDE.md` exists **without** that marker on line 1: skip (user customized it)
 
 **Step 3: Confirm with user**
@@ -171,7 +198,7 @@ Directory-scoped CLAUDE.md files will be generated for:
   test/    -- Test files (Jest + React Testing Library)
   docs/    -- Documentation
 
-Proceed? (These can be customized later -- /setup:refresh will skip files you edit)
+Proceed? (These can be customized later -- /ccp:setup:refresh will skip files you edit)
 ```
 
 **Step 4: Generate files**
@@ -184,7 +211,7 @@ Use these templates based on the detected stack (from Stage 1):
 
 **Next.js project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code for a **Next.js** project.
@@ -200,7 +227,7 @@ This directory contains the application source code for a **Next.js** project.
 
 **Express + TypeScript project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code for an **Express + TypeScript** project.
@@ -216,7 +243,7 @@ This directory contains the application source code for an **Express + TypeScrip
 
 **Python + Django project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code for a **Django** project.
@@ -232,7 +259,7 @@ This directory contains the application source code for a **Django** project.
 
 **Go project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code for a **Go** project.
@@ -248,7 +275,7 @@ This directory contains the application source code for a **Go** project.
 
 **Generic project (unknown framework):**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code.
@@ -266,7 +293,7 @@ This directory contains the application source code.
 
 **Next.js / React project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Tests (test/)
 
 This directory contains automated tests.
@@ -282,7 +309,7 @@ This directory contains automated tests.
 
 **Python + Django project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Tests (tests/)
 
 This directory contains automated tests.
@@ -298,7 +325,7 @@ This directory contains automated tests.
 
 **Go project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Tests (test/)
 
 This directory contains automated tests.
@@ -314,7 +341,7 @@ This directory contains automated tests.
 
 **Generic project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Tests (test/)
 
 This directory contains automated tests.
@@ -331,7 +358,7 @@ This directory contains automated tests.
 ### lib/ template (all stacks)
 
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Shared Libraries (lib/)
 
 This directory contains shared utility functions and libraries.
@@ -349,7 +376,7 @@ This directory contains shared utility functions and libraries.
 
 **Next.js App Router:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # App Directory (app/)
 
 This directory contains Next.js App Router pages and layouts.
@@ -365,7 +392,7 @@ This directory contains Next.js App Router pages and layouts.
 
 **Rails project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # App Directory (app/)
 
 This directory contains the Rails application code.
@@ -381,7 +408,7 @@ This directory contains the Rails application code.
 
 **Generic app/ directory:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Application (app/)
 
 This directory contains the main application code.
@@ -398,7 +425,7 @@ This directory contains the main application code.
 ### api/ template (all stacks)
 
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # API Layer (api/)
 
 This directory contains API endpoints and route handlers.
@@ -415,7 +442,7 @@ This directory contains API endpoints and route handlers.
 ### scripts/ template (all stacks)
 
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Scripts (scripts/)
 
 This directory contains build, development, and maintenance scripts.
@@ -432,7 +459,7 @@ This directory contains build, development, and maintenance scripts.
 ### docs/ template (all stacks)
 
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Documentation (docs/)
 
 This directory contains project documentation.
@@ -458,8 +485,8 @@ Write CLAUDE.md under 100 lines. Sections:
 - **Build & Validate** (8-10 lines): exact commands
 - **Universal Rules** (5-7 lines): project-specific patterns
 - **Forbidden** (4-6 lines): things that break this project
-- **Methodology — GSD** (6-8 lines): reference /gsd: commands
-- **Toolbox — ECC** (6-8 lines): reference /verify, /checkpoint, /save-session, /learn
+- **Methodology — CCP** (6-8 lines): reference /ccp: commands
+- **Toolbox — CCP** (6-8 lines): reference /ccp:verify, /ccp:checkpoint, /ccp:save-session, /ccp:learn
 - **Before ANY work** (2 lines): `npx skills find <keywords>`
 - **Reference Docs & MCP** (3-4 lines): point to docs/, contexts/, registries
 - **Gotchas** (3-5 lines): non-obvious things from scan
@@ -537,8 +564,8 @@ Check MCP registries (github.com/mcp, mcp.so) for relevant servers.
 
 ## Stage 9 — Initialize
 
-- **New project**: Suggest `/gsd:new-project` for roadmap/milestones
-- **Existing project**: Suggest `/gsd:quick "first task"` or `/gsd:discuss-phase 1`
+- **New project**: Suggest `/ccp:new-project` for roadmap/milestones
+- **Existing project**: Suggest `/ccp:quick "first task"` or `/ccp:discuss-phase 1`
 
 ---
 
@@ -548,8 +575,8 @@ Check MCP registries (github.com/mcp, mcp.so) for relevant servers.
 git add CLAUDE.md */CLAUDE.md .claude/ .mcp.json docs/
 git commit -m "chore: add Claude Code Pilot
 
-- GSD methodology (32 commands, 12 agents)
-- ECC toolbox (sessions, learning, verification, quality gates)
+- CCP methodology (32 commands, 12 agents)
+- CCP toolbox (sessions, learning, verification, quality gates)
 - Language rules: [detected]
 - Directory-scoped CLAUDE.md files: [list of directories]
 - MCP auto-configured: [list of detected tools]
@@ -564,16 +591,16 @@ Setup complete!
 Configured:
 - CLAUDE.md — [X]-line project guide
 - [N] directory CLAUDE.md files (src/, test/, ...)
-- GSD — 32 commands, 12 agents, context monitoring, statusline
-- ECC — Sessions, learning, verification, checkpoints, quality gates
-- [N] ECC agents (architect, code-reviewer, security, tdd, ...)
+- CCP — 32 commands, 12 agents, context monitoring, statusline
+- CCP — Sessions, learning, verification, checkpoints, quality gates
+- [N] CCP agents (architect, code-reviewer, security, tdd, ...)
 - [N] language rule sets activated
 - [N] ecosystem skills installed
 - MCP tools: [list of detected/added tools]
 - Safety hooks + desktop notifications
 
-Methodology:  /gsd:discuss → /gsd:plan → /gsd:execute → /gsd:verify
-Quality:      /verify → /checkpoint → /quality-gate
-Persistence:  /save-session → /resume-session → /learn → /evolve
-Update:       /kit:update
+Methodology:  /ccp:discuss → /ccp:plan → /ccp:execute → /ccp:verify
+Quality:      /ccp:verify → /ccp:checkpoint → /ccp:quality-gate
+Persistence:  /ccp:save-session → /ccp:resume-session → /ccp:learn → /ccp:evolve
+Update:       /ccp:update
 ```

package/src/commands/ccp/ship.md

@@ -0,0 +1,23 @@
+---
+name: ccp:ship
+description: Create PR, run review, and prepare for merge after verification passes
+argument-hint: "[phase number or milestone, e.g., '4' or 'v1.0']"
+allowed-tools:
+  - Read
+  - Bash
+  - Grep
+  - Glob
+  - Write
+  - AskUserQuestion
+---
+<objective>
+Bridge local completion → merged PR. After /ccp:verify-work passes, ship the work: push branch, create PR with auto-generated body, optionally trigger review, and track the merge.
+
+Closes the plan → execute → verify → ship loop.
+</objective>
+
+<execution_context>
+@~/.claude/pilot/workflows/ship.md
+</execution_context>
+
+Execute the ship workflow from @~/.claude/pilot/workflows/ship.md end-to-end.

package/src/commands/ccp/skill-create.md

@@ -0,0 +1,172 @@
+---
+name: ccp:skill-create
+description: Analyze local git history to extract coding patterns and generate SKILL.md files. Local version of the Skill Creator GitHub App.
+allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
+---
+
+# /ccp:skill-create - Local Skill Generation
+
+Analyze your repository's git history to extract coding patterns and generate SKILL.md files that teach Claude your team's practices.
+
+## Usage
+
+```bash
+/ccp:skill-create                    # Analyze current repo
+/ccp:skill-create --commits 100      # Analyze last 100 commits
+/ccp:skill-create --output ./skills  # Custom output directory
+/ccp:skill-create --instincts        # Also generate instincts for continuous-learning-v2
+```
+
+## What It Does
+
+1. **Parses Git History** - Analyzes commits, file changes, and patterns
+2. **Detects Patterns** - Identifies recurring workflows and conventions
+3. **Generates SKILL.md** - Creates valid Claude Code skill files
+4. **Optionally Creates Instincts** - For the continuous-learning-v2 system
+
+## Analysis Steps
+
+### Step 1: Gather Git Data
+
+```bash
+# Get recent commits with file changes
+git log --oneline -n ${COMMITS:-200} --name-only --pretty=format:"%H|%s|%ad" --date=short
+
+# Get commit frequency by file
+git log --oneline -n 200 --name-only | grep -v "^$" | grep -v "^[a-f0-9]" | sort | uniq -c | sort -rn | head -20
+
+# Get commit message patterns
+git log --oneline -n 200 | cut -d' ' -f2- | head -50
+```
+
+### Step 2: Detect Patterns
+
+Look for these pattern types:
+
+| Pattern | Detection Method |
+|---------|-----------------|
+| **Commit conventions** | Regex on commit messages (feat:, fix:, chore:) |
+| **File co-changes** | Files that always change together |
+| **Workflow sequences** | Repeated file change patterns |
+| **Architecture** | Folder structure and naming conventions |
+| **Testing patterns** | Test file locations, naming, coverage |
+
+### Step 3: Generate SKILL.md
+
+Output format:
+
+```markdown
+---
+name: {repo-name}-patterns
+description: Coding patterns extracted from {repo-name}
+version: 1.0.0
+source: local-git-analysis
+analyzed_commits: {count}
+---
+
+# {Repo Name} Patterns
+
+## Commit Conventions
+{detected commit message patterns}
+
+## Code Architecture
+{detected folder structure and organization}
+
+## Workflows
+{detected repeating file change patterns}
+
+## Testing Patterns
+{detected test conventions}
+```
+
+### Step 4: Generate Instincts (if --instincts)
+
+For continuous-learning-v2 integration:
+
+```yaml
+---
+id: {repo}-commit-convention
+trigger: "when writing a commit message"
+confidence: 0.8
+domain: git
+source: local-repo-analysis
+---
+
+# Use Conventional Commits
+
+## Action
+Prefix commits with: feat:, fix:, chore:, docs:, test:, refactor:
+
+## Evidence
+- Analyzed {n} commits
+- {percentage}% follow conventional commit format
+```
+
+## Example Output
+
+Running `/ccp:skill-create` on a TypeScript project might produce:
+
+```markdown
+---
+name: my-app-patterns
+description: Coding patterns from my-app repository
+version: 1.0.0
+source: local-git-analysis
+analyzed_commits: 150
+---
+
+# My App Patterns
+
+## Commit Conventions
+
+This project uses **conventional commits**:
+- `feat:` - New features
+- `fix:` - Bug fixes
+- `chore:` - Maintenance tasks
+- `docs:` - Documentation updates
+
+## Code Architecture
+
+```
+src/
+├── components/     # React components (PascalCase.tsx)
+├── hooks/          # Custom hooks (use*.ts)
+├── utils/          # Utility functions
+├── types/          # TypeScript type definitions
+└── services/       # API and external services
+```
+
+## Workflows
+
+### Adding a New Component
+1. Create `src/components/ComponentName.tsx`
+2. Add tests in `src/components/__tests__/ComponentName.test.tsx`
+3. Export from `src/components/index.ts`
+
+### Database Migration
+1. Modify `src/db/schema.ts`
+2. Run `pnpm db:generate`
+3. Run `pnpm db:migrate`
+
+## Testing Patterns
+
+- Test files: `__tests__/` directories or `.test.ts` suffix
+- Coverage target: 80%+
+- Framework: Vitest
+```
+
+## GitHub App Integration
+
+For advanced features (10k+ commits, team sharing, auto-PRs), use the [Skill Creator GitHub App](https://github.com/apps/skill-creator):
+
+- Install: [github.com/apps/skill-creator](https://github.com/apps/skill-creator)
+- Comment `/skill-creator analyze` on any issue
+- Receives PR with generated skills
+
+## Related Commands
+
+- `/instinct-import` - Import generated instincts
+- `/instinct-status` - View learned instincts
+- `/ccp:evolve` - Cluster instincts into skills/agents
+
+---

package/src/commands/ccp/skill-health.md

@@ -0,0 +1,51 @@
+---
+name: ccp:skill-health
+description: Show skill portfolio health dashboard with charts and analytics
+command: true
+---
+
+# Skill Health Dashboard
+
+Shows a comprehensive health dashboard for all skills in the portfolio with success rate sparklines, failure pattern clustering, pending amendments, and version history.
+
+## Implementation
+
+Run the skill health CLI in dashboard mode:
+
+```bash
+node ~/.claude/scripts/skills-health.js --dashboard
+```
+
+For a specific panel only:
+
+```bash
+node ~/.claude/scripts/skills-health.js --dashboard --panel failures
+```
+
+For machine-readable output:
+
+```bash
+node ~/.claude/scripts/skills-health.js --dashboard --json
+```
+
+## Usage
+
+```
+/ccp:skill-health                    # Full dashboard view
+/ccp:skill-health --panel failures   # Only failure clustering panel
+/ccp:skill-health --json             # Machine-readable JSON output
+```
+
+## What to Do
+
+1. Run the skills-health.js script with --dashboard flag
+2. Display the output to the user
+3. If any skills are declining, highlight them and suggest running /ccp:evolve
+4. If there are pending amendments, suggest reviewing them
+
+## Panels
+
+- **Success Rate (30d)** -- Sparkline charts showing daily success rates per skill
+- **Failure Patterns** -- Clustered failure reasons with horizontal bar chart
+- **Pending Amendments** -- Amendment proposals awaiting review
+- **Version History** -- Timeline of version snapshots per skill

package/src/commands/ccp/stats.md

@@ -0,0 +1,18 @@
+---
+name: ccp:stats
+description: Display project statistics — phases, plans, requirements, git metrics, and timeline
+allowed-tools:
+  - Read
+  - Bash
+---
+<objective>
+Display comprehensive project statistics including phase progress, plan execution metrics, requirements completion, git history stats, and project timeline.
+</objective>
+
+<execution_context>
+@~/.claude/pilot/workflows/stats.md
+</execution_context>
+
+<process>
+Execute the stats workflow from @~/.claude/pilot/workflows/stats.md end-to-end.
+</process>