fix(qa-only,qa): name the exploratory read point and finalization order; judge qa with its browser assets

qa-only judges cited 'next section' pointing at the wrong heading, an exploratory
trigger that contradicted its read point, clock ownership in mixed runs and the
unstated order of exploratory section 4 vs reporting. The qa judge penalized the
absent qa-report-template and issue-taxonomy that qa-patterns loads; with them
in, it found issue-taxonomy's dangling 'rule 13' (the consent rule is browser rule 3).

qa/references/issue-taxonomy.md

@@ -77,7 +77,7 @@ For each page visited during a QA session:
 
 1. **Visual scan** — Take a screenshot (the Read-a-page script; `annotatedScreenshot(pg)` when you need ref labels). Look for layout issues, broken images, alignment.
 2. **Interactive elements** — Click every button, link, and control. Does each do what it says?
-3. **Forms** — Fill and submit (non-local target: consent first — rule 13). Test empty submission, invalid data, edge cases (long text, special characters).
+3. **Forms** — Fill and submit (non-local target: consent first — browser rule 3). Test empty submission, invalid data, edge cases (long text, special characters).
 4. **Navigation** — Check all paths in/out. Breadcrumbs, back button, deep links, mobile menu.
 5. **States** — Check empty state, loading state, error state, full/overflow state.
 6. **Console** — Print `CONSOLE_ERRORS=` after interactions. Any new JS errors or failed requests?