kata-quality-gate

Acceptance criteria traceability is enforced by validating that every acceptance criterion has at least one covering test and that tests reference the correct ACs. The quality gate runs checks across traceability, scope, tests, coverage, types, and performance budgets to produce a final go/no-go score.

Scope creep detection flags modifications outside the declared component or file plan, explicitly allowing legitimate generated or implicit test artifacts. It supports per-layer stacked PR workflows by evaluating subsets of acceptance criteria and components per layer while running tests fully.

Performance budgets and type checking are validated through a quality enforcement checklist that verifies best practices, executes tests, checks coverage thresholds, and validates performance budgets when applicable. The gate consolidates these outcomes into a final quality score.

Yes, the quality gate works for both single PR flows and per-layer stacked workflows. For stacked workflows, it performs a final aggregate validation in the last layer to catch orphaned acceptance criteria or components that were not covered.

Executing checks in a specific order ensures evidence-based validation across traceability, scope, best practices, test execution, coverage, types, and performance budgets. This ordered execution is required to consolidate the final go/no-go decision and persist the quality report.

Quality validation reports are persisted by writing the final quality score and evidence to `.ahrena/issues/{n}/06-quality-report.md` and updating the checkpoint status in `.ahrena/workflow/issue-{n}/checkpoint.md` to reflect the go/no-go outcome.