Prepare Test Environment

Give the other QA skills a running app they can drive, and make starting it repeatable, fast, and identical every time — on macOS, Linux, WSL2, or Windows.

This skill is expensive exactly once per repository. It works like a compiler:

• Execute (every run, step 1). A generated entrypoint script already exists → run it and report. No discovery, no reasoning, no model time spent on figuring out the stack again. This is the normal path.
• Generate (first run, --regenerate, or repair — step 2). No script yet (or it failed) → discover how the project runs, generate the entrypoint script with all the fast-bootstrap machinery baked in (reuse checks, build cache, locks, health waits), verify it cold and warm, and record where it lives.

The durable artifacts, and where they are saved: