replay-user-flowslisted

# Record a journey once, re-verify it forever Exploring an app to find a journey is the expensive part, and re-driving it with a model pays that cost again on every change. **Reticle flows** pay it once: the journey is saved with semantic anchors and replayed deterministically afterwards. Needs Reticle wired in the project. Not there? `RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init`, then the [`install-and-verify`](https://github.com/reticlehq/reticle/blob/main/skills/install-and-verify/SKILL.md) skill. ## Record ``` reticle_run({ tool: "reticle_record", sessionId, args: { action: "start", recordingName: "create-task" } }) … drive the golden path with reticle_act / reticle_act_sequence … reticle_run({ tool: "reticle_record", sessionId, args: { action: "stop", recordingName: "create-task" } }) reticle_run({ tool: "reticle_flow_save", sessionId, args: { flowName: "create-task" } }) ``` That writes `.reticle/flows/create-task.json`. **Commit it**: any agent on the repo can then replay it. Annotate the business outcome, not just the clicks, so a replay proves the journey _achieved_ something: ``` reticle_run({ tool: "reticle_annotate", sessionId, args: { flow: "create-task", kind: "intent", text: "create a task and see it in the list" } }) reticle_run({ tool: "reticle_annotate", sessionId, args: { flow: "create-task", kind: "success-state", signal: "task:created" } }) ``` **You do not need to add `data-testid` first.** A step whose element has no te