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-only/sections/manifest.json

@@ -7,7 +7,7 @@
       "id": "exploratory",
       "file": "exploratory.md",
       "title": "Report-only exploratory QA",
-      "trigger": "running selected report-only baseline and exploratory probes without product or test writes"
+      "trigger": "selecting surfaces and later running the selected report-only probes without product or test writes (one Read covers both)"
     },
     {
       "id": "reporting",