Check whether the outcome improved
Exercise every core step
Create a workspace, create a project, create a non-production test key, and run the built-in check in sequence. Pause after each save and reload the setup route. Assert the next action names the remaining step and never exposes a key value after its one-time display.
Interrupt and recover
Use refresh, back navigation, a closed tab, an invalid submission, and a delayed response at each transition. Confirm saved work remains visible and an error explains how to retry. If a state cannot be controlled in the test harness, mark it partial with the missing observation.
Compare roles
Run the setup guide as the owner and a viewer or member fixture when available. Assert hidden actions stay hidden, visible actions remain truthful, and every redirect preserves workspace context. Verify the final sample Signal and linked Work Item are clearly labeled as built-in evidence.
What to carry forward
Accept when each required step resumes from its saved state, failures expose a specific next action, and role boundaries remain intact. Mark optional invitation or agent-profile coverage separately so core setup success does not imply every onboarding branch was verified.
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