玩法测试操作员：API 不够时硬开 UI Playtest Operator

这条用法在做什么What this use does

官方 Playtest Operator：当 API 不够用时，在电脑上硬走产品路径、捕获失败，并交回一份紧凑发现包。与 Bug 复现不同——这是主动压路径，不是跟一张报修走。 Official Playtest Operator: brute-force tests the product path on a computer when APIs are not enough, captures failures, and returns a tight findings pack. Distinct from bug reproduction: this is proactive path-pressing, not following one ticket.

收录理由Why we listed it 官方 Engineering 新角色。现有 bug-repro / Slack 复现是跟报修走；这里是主动玩法压测。 New official Engineering role. Existing bug-repro follows a report; this proactively playtests a path.

上手路径How to start

1. 先跑一次安全范围Run a safe first pass

   先在可撤回、不外发的范围内试跑。本条未批准前：不改生产、不碰真实客户数据、不提 PR；只返回步骤、截图与发现包。。 Try it first in a reversible, non-outbound scope. Until approved: Do not change production, touch real customer data, or open a PR; return steps, screenshots, and a findings pack only..

2. 存 SkillSave a Skill

   这条用法已包含可复用 Skill。跑通安全范围后，立刻把步骤固化下来。 This use already includes a reusable Skill. After the safe pass, lock the steps in.

3. 再上 RoutineThen add a Routine

   输出稳定后再打开例行 / 定时。本条已有例行形态，不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.