From bd3792566d7817b2feb0246be1e5eb2cff16dbaf Mon Sep 17 00:00:00 2001 From: morluto <76467478+morluto@users.noreply.github.com> Date: Thu, 29 Oct 2026 16:05:03 +0800 Subject: [PATCH] docs(skill): clarify scenario pause deadlines (#7961) Co-authored-by: Cursor Agent --- .../reverse-engineer-anything/references/environments.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.agents/skills/reverse-engineer-anything/references/environments.md b/.agents/skills/reverse-engineer-anything/references/environments.md index 990c7be9ee..9df5486c88 100644 --- a/.agents/skills/reverse-engineer-anything/references/environments.md +++ b/.agents/skills/reverse-engineer-anything/references/environments.md @@ -124,9 +124,11 @@ shape, with the application's own locators, paths and headers: } ``` -Give every step a `timeout_ms`. A step without one waits until the scenario -is cancelled, so a locator that never matches hangs the capture, and the -client with it. Match `wait_for` locators to exactly one element. +Give each step that accepts `timeout_ms` a deadline. Without one, a step waits +until it completes or the scenario is cancelled, so a locator that never +matches hangs the capture and the client with it. The `wait_for_timeout` pause +instead uses `duration_ms` and does not accept `timeout_ms`. Match `wait_for` +locators to exactly one element. 1. Sign in through the UI: `fill` the user and password fields (the password as a secret reference), submit, then `wait_for` an element only a signed-in