v3.12.0 - Documentation Overhaul

Documentation Overhaul

Major README revamp with new documentation structure.

New Docs

• Beginners Guide - Plain English guide for non-technical users
• PRD Check - Story validation before coding starts
• Code Check - 5-step verification pipeline details
• Customization - /my-dna, /styleguide, guardrails

README Changes

• Added detailed two-terminal workflow ASCII diagram
• Shows Terminal 1 (Claude CLI) for planning and customization
• Shows Terminal 2 (Execute) with prd-check and loop flow
• Cleaner structure with links to detailed docs

Since v3.6.0

• Circuit breaker and failure accumulation for retry loops
• Structural error detection (DB schema, migrations, connection issues)
• snake_case to camelCase enforcement
• AWS and API skills
• Test directory detection and validation
• Security/scale validation with Claude auto-fix
• Skills format migration (from commands)
• Elixir/Phoenix support
• FastMCP project support improvements

Full Changelog: v3.6.0...v3.12.0

v3.6.0 - FastMCP Support

What's New

FastMCP as First-Class Project Type

Ralph now auto-detects and configures FastMCP (MCP server) projects:

• Auto-detection: Detects fastmcp in pyproject.toml or requirements.txt
• Server module: Parses [project.scripts] to find MCP server entry point
• MCP port: Reads from .env or docker-compose.yml
• Subprojects: Detects Node.js subprojects (e.g., UI builders)
• CLAUDE.md: Includes FastMCP conventions template automatically

New Config Template

Added templates/config/fastmcp.json with MCP-specific settings

Documentation

• Added Supported Project Types table to README
• Added FastMCP config example to docs/RALPH.md

Bug Fixes

• Fixed config template not being copied before auto-configuration
• Unified detection patterns across all files

v3.5.2

What's New

Signs Merge on Setup

• Running npx agentic-loop setup now merges new default signs into existing signs.json instead of skipping
• Existing projects will automatically get new signs (like sign-007 for updating tests when removing UI)

Full Changelog: v3.5.1...v3.5.2

v3.5.1

What's New

Documentation Overhaul

• Complete rewrite of docs/ARCHITECTURE.md as a proper technical breakdown
• Added Table of Contents for easy navigation
• Added Idea to Execution Flow section explaining the full workflow
• Added Project Setup section documenting npx agentic-loop setup
• Added context and explanations for newcomers

Previous Changes (v3.5.0)

• Lean prompt model following Anthropic's guidance on long-running agents
• PRD as single source of truth (schema defined in /prd command)
• URL expansion with {config.urls.backend} syntax
• /idea now delegates to /prd for consistent schema

Full Changelog: v1.8.15...v3.5.1

v1.8.15

Auto-create config on any ralph command

If .ralph/config.json doesn't exist, any ralph command now:

1. Creates the config file
2. Auto-detects project settings (playwright.testDir, directories, etc.)

This ensures config is always set up, even if postinstall was skipped.

v1.8.14

Fix: Postinstall output now visible

npm 7+ suppresses stdout from postinstall scripts. Changed to use stderr so the auto-config message is always shown.

To test, you need to force reinstall:

npm uninstall vibe-and-thrive && npm install vibe-and-thrive

v1.8.13

Shows auto-detected config on install

Now when you run npm install, you'll see what was auto-detected:

  ✨ vibe-and-thrive installed!

  Auto-configured .ralph/config.json:
    e2e tests: apps/web/tests/e2e
    dev server: http://localhost:3000
    frontend: apps/web
    backend: apps/api

  Next steps:
    claude                        # Start Claude Code
    /idea 'your feature'          # Generate a PRD
    ralph run                     # Execute autonomously

v1.8.12

Auto-configuration on npm install

Now when you run npm install vibe-and-thrive, the postinstall script automatically detects and configures:

Setting	How it's detected
playwright.testDir	Scans tests/e2e, apps/*/tests/e2e, etc.
testUrlBase	Parses package.json for dev server port (:3000, :5173, :8080)
directories.frontend	Finds apps/web, frontend, etc.
directories.backend	Finds apps/api, backend, etc.
packageManager	Checks for yarn.lock, pnpm-lock.yaml, bun.lockb

No manual configuration needed for most monorepo projects.

To re-run detection on an existing project:

ralph config

v1.8.11

Features

Auto-detect and configure project settings on ralph init:

Setting	Auto-detection
playwright.testDir	Searches tests/e2e, apps/*/tests/e2e, etc.
testUrlBase	Parses package.json for dev server port
directories.frontend	Finds apps/web, frontend, etc.
directories.backend	Finds apps/api, backend, etc.
packageManager	Detects yarn, pnpm, bun from lockfiles

New Command

ralph config   # Re-run auto-detection on existing project

Example Output

Auto-configuring project settings...
  Auto-detected playwright.testDir: apps/web/tests/e2e
  Auto-detected testUrlBase: http://localhost:3000
  Auto-detected directories.frontend: apps/web
  Auto-detected directories.backend: apps/api

v1.8.10

Fixes

• Playwright test file detection now config-driven (not guessing)
• Add testFile to story in prd.json for explicit path
• Set playwright.testDir in .ralph/config.json for monorepos
• Clear error message shows fix options when test file not found

Config Example

// .ralph/config.json
{
  "playwright": {
    "testDir": "apps/web/tests/e2e"
  }
}

Or per-story:

{
  "id": "TASK-002",
  "e2e": true,
  "testFile": "apps/web/tests/e2e/my-feature.spec.ts"
}