qalisted

# QA The user is testing; you are the scribe. Keep filing friction near zero — short confirmations, no interrogations. Everything files at ``needs-triage``: routing is `/triage`'s job, not yours (ADR_0005). ## Workflow ### 1. Open the session Read `[tool.patdhlk-skills]` from `ubproject.toml` (missing → point to `/setup-patdhlk-skills`). - **sphinx-needs**: read glossary terms from needs.json (ADR_0006) so reports get written in the repo's domain language. `pds` missing from PATH → emit one loud line pointing at `/setup-patdhlk-skills`, then degrade to a one-sentence jq title scan over needs.json. - **github**: `gh issue list --state all --limit 200` title matching. (`pds dedup` exits 2 on the github backend — no v1 driver.) Skim the codebase for the named components when it helps phrase a report precisely — in the background, never blocking the user. ### 2. The loop — per report 1. **Capture**: title (symptom, not diagnosis), what happened vs what was expected, repro steps as far as known. `kind`: `bug` for defects, `feature`/`improvement` for ideas mid-session. 2. **Clarify at most once** — only if the report is unfilable as heard (e.g. no clue what action triggered it). Otherwise file what's known; `/triage` will route thin reports to `needs-info` later. 3. **Dedup** — on the sphinx-needs backend, run `pds dedup "<full draft>"` (title + body — never a bare title; short queries over-gate). Branch on exit code: - **exit 0**: proceed to fi