factory-build-verification

Automate TDD build verification by executing tests in the terminal, parsing errors, and running auto-fix cycles to ensure code compiles and tests pass before marking implementation tasks as complete. This closes the feedback gap where failing code is incorrectly considered finished.

Incremental development requires scoped per-increment verification and full feature aggregate quality gates for tests, lint, type checking, builds, SAST, and seed schema alignment. Features cannot be marked as IMPLEMENTED_AND_VERIFIED until all mandatory security and complexity thresholds are met.

Automated test execution handles error fixing by parsing terminal errors and applying targeted fixes across up to three attempts. This loop runs after each implementation task to resolve compilation failures and ensure tests pass before proceeding.

Yes, build verification supports security compliance by executing dependency audits and secret scans. It enforces mandatory security thresholds and SAST checks during the aggregate quality gate phase to ensure features meet compliance requirements before verification.

The best way to stop recurring errors is through defect pattern cataloging, which automatically detects recurring error patterns during test execution and proposes adding them to a defect prevention catalog. This prevents identical issues from reoccurring in future development cycles.