Regression Workflow

Scenario#

The existing password control no longer responds correctly to keyboard activation. The repair must preserve the intended behavior and add a test that fails on the responsible revision.

Identify the responsible state#

Before choosing the repair, inspect the relevant line or bounded range.

ait blame src/LoginForm.tsx --line 84

The result connects the source line to its responsible Snapshot and available Plan lineage. This evidence answers where the behavior entered history; it does not automatically decide the repair.

Create a new repair Task#

Record a new sprint item for the regression instead of reopening completed work.

# Password Keyboard Regression [plan-ref: login/password-keyboard-regression/root]

- [ ] Restore native keyboard activation and lock it with a regression test. [ref: login/password-keyboard-regression/repair]

ait task start \
  --from docs/sprints/password_keyboard_regression.md#login/password-keyboard-regression/repair \
  --intent "Restore password-control keyboard activation" \
  --base-line main

Prove the repair#

The agent changes only the bounded behavior, adds the regression test, and runs the repository checks in the Task workspace.

4 tests passed

It records a new Snapshot and follows the same configured readiness and closeout path as any other governed change.

ait snapshot create --message "Restore password-control keyboard activation"
ait task land <task-or-change-id>

Recovery rule#

If blame evidence is incomplete or the repair grows beyond the stated scope, stop and re-scope the Task. Do not overwrite unrelated workspace changes or reinterpret a prior completed Task as active work.

See ait blame and Troubleshooting.