@the-bearded-bear/claude-craft 8.23.3 → 8.26.0-next.2a54921

package/Dev/i18n/en/Common/commands/ralph-run.md

@@ -76,6 +76,35 @@ The DoD system validates completion through multiple criteria:
 | `hook` | Run existing Claude hook |
 | `human` | Interactive human validation |
 
+#### `command` validator limit → use `type: hook`
+
+`type: command` only runs commands that pass the allowlist in `Tools/Ralph/lib/dod-validator.sh`: letters, digits, space and `_ . / " ' -`. Any command containing `=`, `|`, `&` or `:` (as well as `;`, `>`, `$`, etc.) is rejected with `ERROR: Invalid command`: the criterion is then **never** met and the loop runs until the circuit breaker trips.
+
+| Rejected command | Offending character |
+|------------------|---------------------|
+| `dotnet build /p:TreatWarningsAsErrors=true` | `:` and `=` |
+| `npm test && npm run lint` | `&` |
+| `pytest \| tee out.log` | `\|` |
+
+For these cases, put the command in a script and declare it as `type: hook`:
+
+```yaml
+definition_of_done:
+  checklist:
+    - id: build
+      type: hook
+      script: ".ralph/dod/build.sh"
+      required: true
+```
+
+```bash
+#!/usr/bin/env bash
+# .ralph/dod/build.sh — receives {"cwd": ..., "output": ...} as JSON on stdin
+dotnet build /p:TreatWarningsAsErrors=true || exit 2
+```
+
+The script returns `0` (criterion met) or `2` (criterion failed). Keys read per type: `command` → `command:`, `output_contains` and `file_changed` → `pattern:`, `hook` → `script:`, `human` → `prompt:`.
+
 ### 4. Adaptive Circuit Breaker (v2.0)
 
 Automatically selects profile based on task keywords:
@@ -100,6 +129,23 @@ Claude works...
 Stop → stop-dod-gate.sh → Block if DoD not satisfied (exit 2)
 ```
 
+## /goal (interactive) or Ralph (autonomous/CI)?
+
+`/goal` is a native Claude Code command typed inside a session: it is not a `ralph.sh` option — `ralph.sh` has none for it and never generates a `/goal`. The two tools are complementary:
+
+| Criterion | `/goal` (native) | Ralph (`ralph.sh`) |
+|-----------|------------------|--------------------|
+| Completion check | LLM judgment: a small fast model evaluates, after each turn, what is visible in the conversation — it runs no command and reads no file | Deterministic: commands, patterns and hooks run by `dod-validator.sh` |
+| Iteration cap | No fixed cap: ends when the condition is met or judged impossible, on `/goal clear`, or if Claude answers several turns in a row without tools; a bound can be written into the condition | `max_iterations` + adaptive circuit breaker |
+| Headless / CI | `claude -p "/goal ..."` loops to completion in a single invocation; CI usage not documented | Built for it: autonomous runs (`--autonomous`, `--overnight`), `headless` dashboard |
+| `disableAllHooks: true` | Unavailable: `/goal` wraps a session-scoped Stop hook (same with `allowManagedHooksOnly`) | The loop and the DoD run inside `ralph.sh`; only the hooks integration (`stop-dod-gate.sh`) is disabled |
+| Configuration | None; one goal per session, cleared by `/clear` | `ralph.yml` |
+
+- **Choose `/goal`** for an interactive task whose completion shows up in the conversation (print the test output: the evaluator does not run it).
+- **Choose Ralph** when completion must be proven by commands, with an iteration cap, unattended or in CI.
+
+Reference: [`/goal` documentation](https://code.claude.com/docs/en/goal).
+
 ## Quick Start Examples
 
 ```bash
@@ -275,4 +321,4 @@ When a timeout fires:
 
 - `@ralph-conductor` - Agent for Ralph orchestration
 - `/qa:tdd` - TDD-based bug fixing
-- `/sprint:dev` - Sprint development with TDD
+- `/workflow:implement` - Sprint development with TDD

package/Dev/i18n/en/Common/commands/release-checklist.md

@@ -1,245 +1,9 @@
 ---
-description: Release Checklist
-argument-hint: [arguments]
+description: "Deprecated (removed in 9.0): use /gate:check release"
+deprecated: true
+replaced-by: /gate:check
 ---
 
-# Release Checklist
+> ⚠️ `/common:release-checklist` is deprecated and will be removed in 9.0. Use `/gate:check release`.
 
-You are an expert Release Manager. You must guide the team through all steps of a quality release, verifying each critical point.
-
-## Arguments
-$ARGUMENTS
-
-Arguments:
-- Version (e.g., `1.2.0`, `2.0.0-beta.1`)
-- Type (patch, minor, major)
-
-Example: `/common:release-checklist 1.2.0 minor`
-
-## MISSION
-
-### Step 1: Pre-Release Validation
-
-#### 1.1 Code State
-```bash
-# Verify on correct branch
-git branch --show-current  # Must be main/master or release/*
-
-# Verify no uncommitted changes
-git status
-
-# Verify all tests pass
-# [Run tests according to technology]
-```
-
-#### 1.2 Changelog
-```bash
-# Verify CHANGELOG.md is up to date
-cat CHANGELOG.md | head -50
-
-# Generate changelog since last tag
-git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"- %s"
-```
-
-#### 1.3 Version Files
-```bash
-# Check/update version files
-# PHP: composer.json
-# Python: pyproject.toml, __version__.py
-# Node: package.json
-# Flutter: pubspec.yaml
-# iOS: Info.plist
-# Android: build.gradle
-```
-
-### Step 2: Exhaustive Tests
-
-```bash
-# Unit tests
-# Integration tests
-# E2E tests
-# Performance tests
-# Security tests
-```
-
-### Step 3: Documentation
-
-```bash
-# Verify documentation
-# - README up to date
-# - API docs generated
-# - Migration guide (if breaking changes)
-```
-
-### Step 4: Generate Interactive Checklist
-
-```
-══════════════════════════════════════════════════════════════
-🚀 RELEASE CHECKLIST - v{VERSION}
-══════════════════════════════════════════════════════════════
-
-Type: {TYPE} (patch/minor/major)
-Date: YYYY-MM-DD
-Branch: main
-
-══════════════════════════════════════════════════════════════
-📋 PRE-RELEASE
-══════════════════════════════════════════════════════════════
-
-## Code Quality
-- [ ] All tests pass (unit, integration, e2e)
-- [ ] Test coverage ≥ 80%
-- [ ] Static analysis without errors
-- [ ] Code review completed on all PRs
-- [ ] No blocking TODO/FIXME
-
-## Security
-- [ ] Dependencies audit (no critical CVEs)
-- [ ] No secrets in code
-- [ ] Security tests passed (OWASP)
-- [ ] Valid SSL certificates
-
-## Documentation
-- [ ] CHANGELOG.md updated
-- [ ] README.md up to date
-- [ ] API documentation generated
-- [ ] Migration guide (if breaking changes)
-- [ ] Release notes written
-
-## Versioning
-- [ ] Version number incremented
-- [ ] Git tags prepared
-- [ ] Release branches created (if applicable)
-
-══════════════════════════════════════════════════════════════
-📦 BUILD & PACKAGE
-══════════════════════════════════════════════════════════════
-
-## Backend
-- [ ] Production build successful
-- [ ] Assets compiled and minified
-- [ ] DB migrations prepared
-- [ ] Environment variables documented
-
-## Frontend Web
-- [ ] Bundle optimized (code splitting, tree shaking)
-- [ ] Assets CDN ready
-- [ ] Service worker updated
-- [ ] Sourcemaps generated (but not deployed to prod)
-
-## Mobile (if applicable)
-- [ ] iOS build signed
-- [ ] Android build signed
-- [ ] Store screenshots updated
-- [ ] Store metadata ready
-
-══════════════════════════════════════════════════════════════
-🔧 STAGING VALIDATION
-══════════════════════════════════════════════════════════════
-
-- [ ] Staging deployment successful
-- [ ] DB migrations executed successfully
-- [ ] Manual smoke tests OK
-- [ ] Regression tests passed
-- [ ] Acceptable performance (< defined thresholds)
-- [ ] Monitoring works (logs, metrics)
-- [ ] Rollback tested
-
-══════════════════════════════════════════════════════════════
-🚀 PRODUCTION DEPLOYMENT
-══════════════════════════════════════════════════════════════
-
-## Pre-Deploy
-- [ ] Maintenance mode activated (if necessary)
-- [ ] Database backup performed
-- [ ] Support team communication
-- [ ] Deployment window validated
-
-## Deploy
-- [ ] Production deployment launched
-- [ ] DB migrations executed
-- [ ] Health checks pass
-- [ ] Maintenance mode deactivated
-
-## Post-Deploy
-- [ ] Production smoke tests OK
-- [ ] Monitoring verified (no errors)
-- [ ] Nominal performance
-- [ ] Git tag created and pushed
-- [ ] GitHub/GitLab release created
-
-══════════════════════════════════════════════════════════════
-📢 COMMUNICATION
-══════════════════════════════════════════════════════════════
-
-- [ ] Release notes published
-- [ ] Support team informed
-- [ ] Clients notified (if applicable)
-- [ ] Public documentation updated
-- [ ] Blog/social media announcement (if applicable)
-
-══════════════════════════════════════════════════════════════
-🔙 ROLLBACK PLAN
-══════════════════════════════════════════════════════════════
-
-In case of critical problem:
-
-1. Identify problem
-   - Logs: [monitoring URL]
-   - Alerts: [alerting URL]
-
-2. Rollback decision
-   - Threshold: > 5% 5xx errors for 5 min
-   - Decision maker: [Name]
-
-3. Execute rollback
-   ```bash
-   # Rollback command
-   [Adapt according to infrastructure]
-   ```
-
-4. DB rollback (if necessary)
-   ```bash
-   # Migrations down
-   [Adapt according to ORM]
-   ```
-
-5. Communication
-   - Notify team
-   - Open incident
-   - Post-mortem
-
-══════════════════════════════════════════════════════════════
-✅ FINAL VALIDATION
-══════════════════════════════════════════════════════════════
-
-[ ] All boxes checked
-[ ] Release validated by: _______________
-[ ] Release date/time: _______________
-
-Notes:
-_________________________________________________
-_________________________________________________
-```
-
-## Useful Commands
-
-```bash
-# Create tag
-git tag -a v{VERSION} -m "Release v{VERSION}"
-git push origin v{VERSION}
-
-# Create GitHub release
-gh release create v{VERSION} --title "v{VERSION}" --notes-file RELEASE_NOTES.md
-
-# Generate automatic changelog
-git-cliff --unreleased --tag v{VERSION} > CHANGELOG.md
-```
-
-## Semantic Versioning Reminder
-
-| Type | When | Example |
-|------|-------|---------|
-| MAJOR | Breaking changes | 1.0.0 → 2.0.0 |
-| MINOR | New feature | 1.0.0 → 1.1.0 |
-| PATCH | Bug fix | 1.0.0 → 1.0.1 |
+Run `/gate:check release $ARGUMENTS`: read `.claude/commands/gate/check.md` and follow it with these arguments. If that file is missing, reinstall claude-craft with project management.

package/Dev/i18n/en/Common/commands/setup-project-context.md

@@ -1,290 +1,9 @@
 ---
-name: setup-project-context
-description: Analyze codebase and configure project context interactively
-arguments:
-  - name: mode
-    description: Detection mode (--auto minimal questions, --full comprehensive)
-    required: false
+description: "Deprecated (removed in 9.0): use /common:init --context"
+deprecated: true
+replaced-by: /common:init
 ---
 
-# Setup Project Context
+> ⚠️ `/common:setup-project-context` is deprecated and will be removed in 9.0. Use `/common:init --context`.
 
-Configure `.claude/rules/00-project-context.md` by analyzing the codebase and asking targeted questions.
-
-## Execution
-
-### Phase 1: Automatic Detection
-
-Analyze the following files and directories:
-
-**Configuration Files:**
-- `package.json` → Node.js project name, dependencies, scripts
-- `composer.json` → PHP project name, dependencies, framework
-- `pubspec.yaml` → Flutter/Dart project name, dependencies
-- `requirements.txt` / `pyproject.toml` → Python dependencies
-- `Cargo.toml` → Rust project
-- `go.mod` → Go module
-
-**Environment & Config:**
-- `.env`, `.env.example` → Database, services
-- `config/` → Framework configuration
-- `docker-compose.yml` → Services (DB, Redis, etc.)
-
-**Structure:**
-- `src/`, `lib/`, `app/` → Source code location
-- `tests/`, `spec/` → Testing framework
-- `docs/`, `specifications/` → Documentation
-- `.github/`, `.gitlab-ci.yml` → CI/CD
-
-**Domain (if applicable):**
-- `src/Entity/`, `src/Domain/` → Business entities (PHP/Symfony)
-- `lib/models/`, `lib/domain/` → Models (Flutter/Dart)
-- `models/`, `schemas/` → Data models
-- `migrations/` → Database schema
-
-Display analysis results:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║                 PROJECT ANALYSIS RESULTS                      ║
-╚══════════════════════════════════════════════════════════════╝
-
-✅ Detected Information:
-┌─────────────────┬────────────────────────────────┐
-│ Element         │ Value                          │
-├─────────────────┼────────────────────────────────┤
-│ Project Name    │ {detected_name}                │
-│ Language        │ {detected_language}            │
-│ Framework       │ {detected_framework}           │
-│ Database        │ {detected_database}            │
-│ Testing         │ {detected_testing}             │
-│ CI/CD           │ {detected_cicd}                │
-└─────────────────┴────────────────────────────────┘
-
-📁 Project Structure:
-{detected_structure}
-
-📄 Documentation Found:
-{detected_docs}
-
-❌ Not Detected (will ask):
-- {missing_items}
-```
-
-### Phase 2: Interactive Questions
-
-Ask only for information NOT detected in Phase 1.
-Skip questions if `--auto` mode is used and a reasonable default exists.
-
-**Essential Questions:**
-
-1. **Application Type** (if not detected):
-   ```
-   What type of application is this?
-   [ ] REST API      [ ] Web Application    [ ] Mobile App
-   [ ] CLI Tool      [ ] Library/Package    [ ] Monorepo
-   ```
-
-2. **Business Domain**:
-   ```
-   What is the business domain?
-   [ ] E-commerce    [ ] SaaS Platform      [ ] FinTech
-   [ ] HealthTech    [ ] EdTech             [ ] Social/Community
-   [ ] Media/Content [ ] IoT                [ ] Other: _____
-   ```
-
-3. **Target Users** (2-3 personas):
-   ```
-   Describe your main users:
-
-   Primary User:
-   > Role: _____
-   > Main goal: _____
-
-   Secondary User (optional):
-   > Role: _____
-   > Main goal: _____
-   ```
-
-4. **Compliance Requirements**:
-   ```
-   Which compliance requirements apply?
-   [ ] GDPR (EU data protection)
-   [ ] HIPAA (US healthcare)
-   [ ] PCI-DSS (Payment card)
-   [ ] SOC2 (Security)
-   [ ] None / Not applicable
-   ```
-
-**Extended Questions** (only with `--full` mode):
-
-5. **Business Goals**:
-   ```
-   Short-term goals (3-6 months):
-   > _____
-
-   Medium-term goals (6-12 months):
-   > _____
-   ```
-
-6. **Known Issues/Technical Debt**:
-   ```
-   Any known issues or technical debt to document?
-   > _____
-   ```
-
-7. **Glossary Terms**:
-   ```
-   Key business terms to define (comma-separated):
-   > _____
-   ```
-
-### Phase 3: Generate Context File
-
-Create `.claude/rules/00-project-context.md`:
-
-```markdown
-# Project Context - {PROJECT_NAME}
-
-> Auto-generated by `/common:setup-project-context` on {DATE}
-> Review and customize as needed.
-
-## Plan Mode
-
-> **Plan mode is recommended.** Claude activates plan mode to structure the approach, identify dependencies, and present a generation strategy before creating artifacts.
-
-## Overview
-
-**{PROJECT_NAME}** is a {TYPE} application for the {DOMAIN} domain.
-
-{DESCRIPTION_FROM_README_OR_USER}
-
-## Technical Stack
-
-| Component    | Technology           |
-|--------------|----------------------|
-| Language     | {LANGUAGE}           |
-| Framework    | {FRAMEWORK}          |
-| Database     | {DATABASE}           |
-| Cache        | {CACHE_IF_DETECTED}  |
-| Testing      | {TESTING_FRAMEWORKS} |
-| CI/CD        | {CICD_PLATFORM}      |
-
-## Project Structure
-
-```
-{DETECTED_STRUCTURE}
-```
-
-## Business Domain
-
-### Core Concepts
-
-{ENTITIES_IF_DETECTED}
-
-### Bounded Contexts
-
-<!-- Add if using DDD -->
-- Context 1: ...
-- Context 2: ...
-
-## Users & Personas
-
-### {PRIMARY_USER_ROLE}
-- **Goal:** {PRIMARY_USER_GOAL}
-- **Pain points:** To be documented
-- **Key workflows:** To be documented
-
-### {SECONDARY_USER_ROLE}
-- **Goal:** {SECONDARY_USER_GOAL}
-- **Pain points:** To be documented
-- **Key workflows:** To be documented
-
-## Constraints
-
-### Compliance
-{COMPLIANCE_REQUIREMENTS}
-
-### Performance Targets
-- Page load time: < 3s
-- API response time: < 200ms
-- Availability: 99.9%
-
-### Security Requirements
-- OWASP Top 10 compliance
-- Input validation on all endpoints
-- Authentication required for protected resources
-
-## Goals
-
-### Short-term
-{SHORT_TERM_GOALS_OR_PLACEHOLDER}
-
-### Medium-term
-{MEDIUM_TERM_GOALS_OR_PLACEHOLDER}
-
-## Known Issues / Technical Debt
-
-{ISSUES_OR_PLACEHOLDER}
-
-## Glossary
-
-| Term | Definition |
-|------|------------|
-{GLOSSARY_TERMS_OR_EXAMPLES}
-```
-
-### Phase 4: Validation & Next Steps
-
-Display summary and recommendations:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║              PROJECT CONTEXT GENERATED                        ║
-╚══════════════════════════════════════════════════════════════╝
-
-✅ File created: .claude/rules/00-project-context.md
-
-Summary:
-┌─────────────────┬────────────────────────────────┐
-│ Project         │ {PROJECT_NAME}                 │
-│ Type            │ {TYPE}                         │
-│ Stack           │ {FRAMEWORK} + {DATABASE}       │
-│ Domain          │ {DOMAIN}                       │
-│ Compliance      │ {COMPLIANCE}                   │
-│ Personas        │ {COUNT} defined                │
-└─────────────────┴────────────────────────────────┘
-
-📋 Recommended Next Steps:
-
-1. Review generated file and complete placeholder sections
-2. Add detailed bounded contexts if using DDD
-3. Document key business workflows
-4. Consider running specialized agents:
-   - @database-architect → Document database schema
-   - @api-designer → Document API endpoints
-   - @security-reviewer → Review security constraints
-
-Would you like me to open the file for review?
-```
-
-## Modes
-
-| Mode | Behavior |
-|------|----------|
-| (default) | Detect + essential questions (type, domain, users, compliance) |
-| `--auto` | Maximum auto-detection, skip questions with reasonable defaults |
-| `--full` | All questions including goals, issues, and glossary |
-
-## Examples
-
-```bash
-# Standard mode - balanced detection and questions
-/common:setup-project-context
-
-# Auto mode - minimal interaction
-/common:setup-project-context --auto
-
-# Full mode - comprehensive questionnaire
-/common:setup-project-context --full
-```
+Run `/common:init --context $ARGUMENTS`: read `.claude/commands/common/init.md` and follow it with these arguments.

package/Dev/i18n/en/Common/rules/12-context-management.md

@@ -386,7 +386,7 @@ Session 2: Implementation (code, test)
 The `/loop` command allows scheduling recurring tasks:
 
 ```bash
-/loop 5m /common:pre-commit-check    # Check every 5 minutes
+/loop 5m /gate:check commit    # Check every 5 minutes
 /loop "Monitor CI tests"              # Auto-paced by the model
 ```
 

package/Dev/i18n/en/QA/commands/fix.md

@@ -227,19 +227,19 @@ resume_from:
 
 ```bash
 # Fix all bugs from a recette session
-/qa:recette-fix --session=REC-20260130-143022
+/qa:fix --session=REC-20260130-143022
 
 # Dry run: refine and document without fixing
-/qa:recette-fix --session=REC-20260130-143022 --dry-run
+/qa:fix --session=REC-20260130-143022 --dry-run
 
 # Fix only critical and high severity bugs
-/qa:recette-fix --session=REC-20260130-143022 --severity=high
+/qa:fix --session=REC-20260130-143022 --severity=high
 
 # Generate BMAD documents without launching TDD
-/qa:recette-fix --session=REC-20260130-143022 --skip-fix
+/qa:fix --session=REC-20260130-143022 --skip-fix
 
 # Fix with automatic commits
-/qa:recette-fix --session=REC-20260130-143022 --auto-commit
+/qa:fix --session=REC-20260130-143022 --auto-commit
 ```
 
 ## Output Structure
@@ -269,9 +269,9 @@ resume_from:
 | Command | Description |
 |---------|-------------|
 | `/qa:recette` | Execute acceptance tests |
-| `/qa:recette-status` | Show session status |
-| `/qa:recette-regression` | View regression tests |
-| `/qa:recette-report` | Generate report |
+| `/qa:status` | Show session status |
+| `/qa:regression` | View regression tests |
+| `/qa:status --report` | Generate report |
 
 ## Error Messages
 

package/Dev/i18n/en/QA/commands/recette.md

@@ -214,12 +214,11 @@ entries:
 
 | Command | Description |
 |---------|-------------|
-| `/qa:recette-fix` | Fix bugs from a recette session |
-| `/qa:recette-status` | Show session status |
-| `/qa:recette-regression` | View regression tests |
-| `/qa:recette-report` | Generate report |
-| `/qa:validate` | Validate story AC |
-| `/qa:automate` | Create automated tests |
+| `/qa:fix` | Fix bugs from a recette session |
+| `/qa:status` | Show session status |
+| `/qa:regression` | View regression tests |
+| `/qa:status --report` | Generate report |
+| `/gate:check story` | Validate story AC |
 
 ## Chrome Capabilities
 
@@ -262,9 +261,9 @@ entries:
 ║    Fix bugs with TDD approach                            ║
 ║                                                          ║
 ║  If all tests pass:                                      ║
-║  → /qa:report                                            ║
+║  → /qa:status --report                                            ║
 ║    Generate the recette report                           ║
-║  → /sprint:transition done                               ║
+║  → /project:backlog move story done                               ║
 ║    Mark the story as done                                ║
 ║                                                          ║
 ╚══════════════════════════════════════════════════════════╝