What problem does it solve?
Provides a deterministic, real-system validation runner that removes reliance on mocks and fragile unit-only checks by executing end-to-end journeys against the actual application, capturing verifiable evidence, and iteratively repairing failures until stability or a hard abort.
Core Features & Use Cases
- Autonomous Forge Loop: Orchestrates PLAN → PREFLIGHT → EXECUTE → ANALYZE → FIX → REBUILD → RE-EXECUTE with a three-strike limit per journey.
- Per-Attempt Evidence: Creates isolated evidence directories for each attempt (e2e-evidence/forge-attempt-{N}/{journey-slug}/) and records outcomes and fixes in persistent state.
- Safe Rebuild & Retry Rules: Enforces a required build step before any re-validation, supports full/quick/ci/targeted modes, and emits CI-friendly exit codes.
- State Persistence & Reporting: Persists run and journey state to .validationforge/forge-state.json and generates a unified report at e2e-evidence/report.md.
- Use Case: Run in CI to detect regressions that unit tests miss, or run locally to validate and iteratively fix a failing login or settings journey while preserving evidence.
Quick Start
Start the autonomous validation loop by running forge-execute after creating a validation plan so it captures per-attempt evidence, attempts fixes up to three strikes, and produces a unified report.