qalisted

<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # QA Exercise the product as a user or consumer would. Default to reproducing and reporting findings. `--fix` or an explicit repair request authorizes fixing confirmed bugs and retesting. Run this workflow yourself; do not dispatch agents by default. ## Instructions ### 1. Resolve the feature and execution surface An explicit target wins. Otherwise infer the **last developed feature** from the current conversation and its acceptance criteria, corroborated by relevant local changes. Read `AGENTS.md`, startup instructions, feature docs, and existing manual test procedures. Inspect `git status --short`, staged/unstaged diffs, relevant untracked files, and recent commits as needed. On a clean tree, follow the latest coherent feature across commits; the newest commit may only be a fix or formatting. Do not assume a feature branch, an upstream, or a branch named `main`. State the selected feature, evidence for that choice, and affected interfaces. Include adjacent behavior sharing the changed boundary. Avoid turning a default run into a whole-project audit. If several unrelated features remain equally plausible, ask one scope question while continuing environment discovery. In a multi-repo workspace, resolve the target repository first. Identify the actual build/URL/device/binary and the documented way to run it. Read only the applicable adapter(s): | Surface | Adapter | |---|