Remove an apostrophe the embedded-script guard caught

The comment explaining the perQuery fix contained "each query's results",
inside a node -e '...' block. That apostrophe would end the shell string on
the runner - the exact failure that broke the first live collection on
"run's" and caused this guard to be written.

Caught by the guard rather than by a red run, which is what it is for.

855 passed, 0 failed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: StepenkoAnatoli

.github/workflows/collect.yml

@@ -374,8 +374,8 @@ jobs:
             const plan = JSON.parse(fs.readFileSync("research/plan.json", "utf8"));
             plan.topic = topic;
             plan.maxScrapes = Number(process.env.MAX_PAGES);
-            // perQuery is the REAL ceiling on breadth: selectCandidates slices each
-            // query's results to it, so one seeded query and the scaffold default of 3
+            // perQuery is the REAL ceiling on breadth: selectCandidates slices the
+            // results of each query to it, so one seeded query and a default of 3
             // capped every dispatched run at three candidates however large max_pages
             // was. Matching it to max_pages is what makes the advertised 1..25 control
             // mean what it says. Nothing about SPEND changes - maxScrapes still bounds