implementlisted

Generate Playwright TypeScript test code from `test-plan.md`. ## Usage ``` /verefi:implement [--name <run-name>] [--tc TC-001] ``` ## What this does Read `test-plan.md` (plus `discovery.md` and `audit.md` if present), make sure the repo has a single root-level Playwright setup, then generate a complete, runnable spec file into the repo's shared, **committed** test suite. The generated tests are the pipeline's durable end product — they live at repo root and get merged in a PR; the `.verefi/<name>/` artifacts are the disposable review-gate scratch that got them there. ## Run name `<name>` defaults to the sanitized current git branch (same rule as every other stage), with `--name` as an explicit override: ```bash name=$(git branch --show-current 2>/dev/null | sed 's/[^a-zA-Z0-9._-]/-/g') if ! [[ "$name" =~ ^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$ ]]; then name=default; fi ``` If `--name` is supplied, **reject it** unless it exactly matches `^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$`. Do not sanitize an explicit value. Validate before reading or writing any `.verefi/<name>/` path or generated spec filename. ## Inputs — the selector trust hierarchy - **Required:** `.verefi/<name>/test-plan.md` — the test plan from `/verefi:testplan` - **Optional:** `.verefi/<name>/discovery.md` — selectors verified against the live app by `/verefi:discover` (or written by hand). Also read its Section 2 (Gaps) and Section 3 (Behavioral Findings) — see Step 1b. - **Optional:** `.verefi/<name>/audit.md`