mission-validation

Automated milestone validation runs tests, type checks, and linting against defined assertions. It initiates a self-correction loop by creating and executing fix features for any failed checks before sealing the milestone.

Automated checks and user surface testing verify code quality by executing tests, analyzing git diffs, and testing actual interfaces against expected behavior to ensure all milestone requirements are met.

A self-correction loop handles failed assertions by automatically identifying the failures, creating fix features, executing them, and re-validating until all assertions pass during the code review.

Yes, milestone validation runs automated checks including type checks and linting without manual intervention, implementing a self-correction loop to address any failed assertions by creating and executing fixes automatically.

You should seal a milestone after completing an end-gate check once all assertions pass. The final milestone is sealed only when automated checks, code reviews, and user surface testing confirm successful validation.

Milestone validation fails when automated checks, code reviews, or user surface testing detect unmet assertions. The self-correction loop fixes it by creating and executing fix features, then re-validating until all assertions pass.