QA Clear: $ARGUMENTS
Human QA can only judge what a user can see. Tickets whose entire scope is a
non-user-facing repo were already verified by the automated lifecycle before reaching the
QA queue; holding them for a human who cannot observe them is pure queue noise. Clear
them in one auditable batch.
Config resolution
Read .lisa.config.json:
- QA queue status —
jira.workflow.qa.queue, falling back to
jira.workflow.done.staging.
- Certified status —
jira.workflow.qa.certified. Required; if missing, stop and
instruct the operator — never guess a terminal status.
- Tracker dispatch —
tracker decides the surface as everywhere; on GitHub or
Linear the status names above map to the equivalent labels/states.
- Non-user-facing repos —
qa.nonUserFacingRepos (array of repo names, e.g.
["api", "infrastructure"]). If the key is missing, derive a proposal from
the project registry (repos with no UI framework signals — no expo/react/native/web
app surface) and present it for operator confirmation before moving anything; never
bulk-transition on an unconfirmed inference. Recommend persisting the confirmed list to
the config.
Procedure
- Query all tickets in the QA queue status.
- Classify each by repo scope, in order:
repo:<name> label or matching component → that repo.
- Unlabeled → determine the repo from the ticket content (description, AC, technical
approach) exactly as build-intake's repo-scope gate does, and stamp the
repo:<name> label while you're there so the next sweep is cheap.
- Undeterminable → leave in place; flag for the operator.
- Partition:
- Every touched repo is non-user-facing → eligible to clear.
- Any user-facing repo in scope (including mixed-scope) → stays in the queue for the
human pass via
lisa-qa-queue.
- For each eligible ticket, in this order — the pairing must be failure-safe:
Post the audit comment first:
[lisa-qa-clear] Certified without human QA: scope is <repo(s)>, not observable with end-user access. Verified by the automated lifecycle pre-promotion.
Then transition to the certified status.
Then clear the QA-failure signal, because certifying is one of its two void
conditions and this is the second path that reaches it:
RESOLVER="${CLAUDE_PLUGIN_ROOT:-${PLUGIN_ROOT:-plugins/lisa}}/scripts/qa-signal-lifecycle.mjs"
SIGNAL=$(node "$RESOLVER" --vendor "<jira|linear|github>" --print-label)
Remove $SIGNAL through the same tracker surface that applied it. Removing a label
the ticket does not carry is a no-op, so this runs unconditionally. The
[lisa-qa-fail] comments are never touched — the history stays, the signal goes.
Verify all three landed before counting the ticket as moved. A comment without
the transition, a transition without the comment, or a certified ticket still
wearing the signal is a partial — report it as such, never as completed.
- Report the batch:
## QA Clear — <date>
Moved to <certified>: <n> (<KEY-1>, <KEY-2>, …) — repo per ticket
Left in queue (user-facing): <n>
Left in queue (undeterminable repo — needs operator): <keys or none>
The operator (or tester) reviews the moved list; anything that "sounds user-facing" can
be pulled back with a single instruction — the transition is reversible and the comment
marks exactly what was auto-cleared.
Rules
- Never clear a mixed-scope ticket — partial human-verifiability means human QA.
- Never bulk-move on an inferred repo list without explicit operator confirmation.
- Every cleared ticket carries the audit comment; a transition without the comment is a
bug in this procedure.
- Idempotent by repair, not by skip: a ticket is complete only when it has the
[lisa-qa-clear] comment, the certified status, AND no QA-failure signal. Re-runs
finish partials — comment present but not certified → transition it; certified but no
comment → post the comment; certified but still signalled → clear the signal. Only
fully-complete tickets are skipped silently.
1---2name: lisa-qa-clear-33description: Bulk-clear tickets a human QA…4---56# QA Clear: $ARGUMENTS78Human QA can only judge what a user can see. Tickets whose entire scope is a9non-user-facing repo were already verified by the automated lifecycle before reaching the10QA queue; holding them for a human who cannot observe them is pure queue noise. Clear11them in one auditable batch.1213## Config resolution1415Read `.lisa.config.json`:1617- **QA queue status** — `jira.workflow.qa.queue`, falling back to18 `jira.workflow.done.staging`.19- **Certified status** — `jira.workflow.qa.certified`. Required; if missing, stop and20 instruct the operator — never guess a terminal status.21- **Tracker dispatch** — `tracker` decides the surface as everywhere; on GitHub or22 Linear the status names above map to the equivalent labels/states.23- **Non-user-facing repos** — `qa.nonUserFacingRepos` (array of repo names, e.g.24 `["api", "infrastructure"]`). If the key is missing, derive a proposal from25 the project registry (repos with no UI framework signals — no expo/react/native/web26 app surface) and **present it for operator confirmation before moving anything**; never27 bulk-transition on an unconfirmed inference. Recommend persisting the confirmed list to28 the config.2930## Procedure31321. Query all tickets in the QA queue status.332. Classify each by repo scope, in order:34 - `repo:<name>` label or matching component → that repo.35 - Unlabeled → determine the repo from the ticket content (description, AC, technical36 approach) exactly as build-intake's repo-scope gate does, and stamp the37 `repo:<name>` label while you're there so the next sweep is cheap.38 - Undeterminable → leave in place; flag for the operator.393. Partition:40 - **Every** touched repo is non-user-facing → eligible to clear.41 - Any user-facing repo in scope (including mixed-scope) → stays in the queue for the42 human pass via `lisa-qa-queue`.434. For each eligible ticket, in this order — the pairing must be failure-safe:44 1. Post the audit comment first:45 `[lisa-qa-clear] Certified without human QA: scope is <repo(s)>, not observable46 with end-user access. Verified by the automated lifecycle pre-promotion.`47 2. Then transition to the certified status.48 3. Then clear the QA-failure **signal**, because certifying is one of its two void49 conditions and this is the second path that reaches it:5051 ```bash52 RESOLVER="${CLAUDE_PLUGIN_ROOT:-${PLUGIN_ROOT:-plugins/lisa}}/scripts/qa-signal-lifecycle.mjs"53 SIGNAL=$(node "$RESOLVER" --vendor "<jira|linear|github>" --print-label)54 ```5556 Remove `$SIGNAL` through the same tracker surface that applied it. Removing a label57 the ticket does not carry is a no-op, so this runs unconditionally. The58 `[lisa-qa-fail]` comments are never touched — the history stays, the signal goes.59 4. Verify all three landed before counting the ticket as moved. A comment without60 the transition, a transition without the comment, or a certified ticket still61 wearing the signal is a **partial** — report it as such, never as completed.625. Report the batch:6364```text65## QA Clear — <date>66Moved to <certified>: <n> (<KEY-1>, <KEY-2>, …) — repo per ticket67Left in queue (user-facing): <n>68Left in queue (undeterminable repo — needs operator): <keys or none>69```7071The operator (or tester) reviews the moved list; anything that "sounds user-facing" can72be pulled back with a single instruction — the transition is reversible and the comment73marks exactly what was auto-cleared.7475## Rules7677- Never clear a mixed-scope ticket — partial human-verifiability means human QA.78- Never bulk-move on an inferred repo list without explicit operator confirmation.79- Every cleared ticket carries the audit comment; a transition without the comment is a80 bug in this procedure.81- Idempotent by repair, not by skip: a ticket is complete only when it has the82 `[lisa-qa-clear]` comment, the certified status, AND no QA-failure signal. Re-runs83 finish partials — comment present but not certified → transition it; certified but no84 comment → post the comment; certified but still signalled → clear the signal. Only85 fully-complete tickets are skipped silently.