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).

test/skill-llm-eval.test.ts

@@ -203,7 +203,8 @@ describeIfSelected('QA skill quality evals', ['qa/SKILL.md workflow', 'qa/SKILL.
     const t0 = Date.now();
     const section = readWorkflowJudgeInput({ root: ROOT, skillPath: 'qa/SKILL.md',
       startMarker: '# /qa: Test', endMarker: null,
-      references: ['qa/templates/functional-report-template.md'] }).text;
+      // qa-patterns.md loads both browser assets; judges penalized their absence.
+      references: ['qa/templates/functional-report-template.md', 'qa/templates/qa-report-template.md', 'qa/references/issue-taxonomy.md'] }).text;
 
     const samples = await judgePanel(() => callJudge<JudgeScore>(`You are evaluating the quality of a QA testing workflow document for an AI coding agent.