Keep the lesson for the next incident
Document setup states
Name the durable states for workspace, project, test key, and built-in check, along with the action allowed from each. Explain optional steps separately. Include the state shown after a failed submission and after a return to an established workspace.
Keep resume fixtures
Save synthetic journeys that pause after every core step, refresh, return later, and complete the check. Assert page heading, next action, workspace context, and evidence label. Link fixtures to the work record without storing secrets or personal registration data.
Define recurrence signals
Reopen review when a saved step disappears, a redirect lands in another workspace, or a core action becomes optional-looking. State role, viewport, and interruption limits, and assign an owner for any new setup transition that lacks a recovery test.
What to carry forward
Close learning with named setup states, interruption fixtures, role coverage, and recurrence triggers. Keep voluntary pauses and untested external timing explicit so the library records a useful contract rather than treating every unfinished guide as a defect.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow