Output style (plain words, no dashes, no hyphens)

Write everything this skill produces, files and messages alike, in plain simple language. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only, not read-only. Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. A structural separator inside a template format other skills parse, such as the em dash in ## Phase 1 — <NAME>, is part of that format: reproduce it exactly, since changing it breaks the mirroring. Use short sentences, commas, or parentheses. Clear beats clever.

What this skill does

The regression gate. It reads .konteksto/audit-register.md and reruns the documented reproduction or acceptance case for audit findings that have a runtime behavior to test.

A bare /dev-qa checks every bug or regression in state ready for QA or verified. /dev-qa AUD-012 checks only that issue. Reject an unknown ID, a non bug or regression issue, or an issue without a reproducible case rather than guessing what to test.

A rejected issue is not a stuck one, and saying so matters. A finding with no runtime case belongs in resolved, which /dev-audit sets and this skill never touches. So when an ID is rejected for its type, say that its state is /dev-audit's to settle and route it there, rather than reporting the run as blocked. A rejection here used to read as a dead end, and a harness demo stalled on exactly that reading.

If the audit register does not exist, report that there are no registered bugs to check. That is a successful no work result, not a reason to block a new project.

Ownership

This skill appends QA Runs rows in .konteksto/audit-register.md. It may update only the selected issue's Status after its own run: ready for QA to verified on PASS, or ready for QA or verified to reopened on FAIL. It never changes any other issue field, fixes code, changes review findings, or writes test files. /dev-test owns regression tests; if a repeatable automated test is missing, report the gap and route it there.