auditlisted

Statically inventory the target repo's stable selectors and grade its testability. ## Usage ``` /verefi:audit [--name <run-name>] [--dir <path>] ``` ## What this does Scan the target app's source (the project you're generating tests *for* — the current working directory, or `--dir` — not this plugin) for evidence of stable selectors, and write `.verefi/<name>/audit.md`. No running app, no credentials, no browser — this takes seconds and works on any repo. Audit exists to make the pipeline's worst failure mode impossible: generating a full suite of fabricated selectors because nothing ever checked whether the codebase has any. It establishes the middle tier of the selector trust hierarchy: > `discovery.md` (live-verified) > `audit.md` (static evidence from source) > Implementation Notes (guess) It's also the pipeline's zero-setup entry point — a testability grade you can produce on a repo you just cloned. ## 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 using it in any `.verefi/<name>/` path. ## Trust boundary Only inspect local source that the user has placed i