qa-bug

Record and reassess a defect

Record defect facts without changing the product. Preserve reproduction, triage, scope, evidence, attempt history, and retest semantics under the governing contract. Read workflow, safety, artifacts, and evidence first.

Inputs

• Project root, target/environment/build/change identity, explicit objective or intent, identified contract source/hash, and the complete supplied criterion catalog with exact IDs, text, applicability, and current results.
• Stable defect ID, summary, prerequisites, exact reproduction steps and data, frequency, expected and observed behavior, affected surface, in-scope/out-of-scope decision, and local target-bound evidence.
• Severity and priority proposals with separate rationales, owner, current state, linked criterion IDs or an explicit unlinked reason, related risks, and complete current-defect inventory.
• Stable logical case ID, original failure and all retest attempts with unique attempt IDs, increasing attempt numbers, supersession links, evidence, and explicit authorization for this write operation or any separately requested retest execution.

Procedure

1. Preserve the explicit objective or intent, target, environment/build, contract, criterion IDs/text, defect identity, existing attempts, approvals, and authorization exactly. Do not infer expected behavior, applicability, resolution, risk acceptance, or execution permission.
2. Identify affected surfaces and consult the installed applicable qa-specialist-* skills, starting with qa-specialist-defects; consult requirements, functional, API, Web, mobile, data, security, performance, automation, CI/CD, regression, or production specialists only when their surfaces apply. An unavailable applicable specialist is a limitation. Specialist guidance cannot expand authorization.
3. Materialize reproduction with prerequisites, ordered steps/actions, safe data, environment and build, frequency, expected oracle, observed mismatch, scope and rationale, criterion links or explicit unlinked reason, risk links, and verified evidence references. Insufficient reproduction or evidence is BLOCKED; never manufacture certainty.
4. Assess severity from product/user impact and blast radius. Assess priority independently from delivery order, urgency, dependencies, and scheduling. Record both rationales, owners, and scope; neither value rewrites the other, the defect status, or the QA result.
5. Preserve the original failure and every retest as immutable history. Use one stable logical case ID, unique attempt IDs, strictly increasing attempt numbers, the same target, and a linear supersedes chain. Never delete a failure, branch/cycle history, or rerun until green.
6. Record a retest result only from an explicitly authorized qa-test execution and valid local, confined, target/contract-bound, integrity-checked, sanitized evidence. This write workflow does not itself execute a stored command or product correction.
7. Mark this defect resolved only when the referenced terminal retest attempt is PASS with valid current evidence; a blocked/failed terminal attempt never falls back to an older pass. Return global PASS only after the terminal retest is valid and has valid current evidence, all applicable criteria are PASS, no pending work or limitations remain, and no other current in-scope defects remain. Missing criteria or defect inventory is BLOCKED; another proven current in-scope defect is FAIL.
8. Apply verdict precedence: any proven current in-scope failure, including an unlinked defect, is FAIL; without such proof, missing reproduction, evidence, retest, or complete inventories is BLOCKED. qa_report.py report --manifest PATH --project-root PATH is a later inert export and the report does not execute or re-run tests.