fix(refresh): report an assumed-robots host once, not twice

The run just made reported each of the four Fandom hosts twice — once from the
warning pushed in runRefresh and once from a second loop in main() that printed
summary.assumedRobots again. Eight lines for four facts, and the header above
them said "5 warnings" while nine printed under it, so the count a reader uses
to judge whether to read the list was wrong in the direction that matters.

Mine, from the commit that added the flag: I put the reminder in main() to make
it loud, having already made it loud in the summary.

The instruction folds into the single warning instead, so it still says to go
re-read the file in a browser, and it now also reaches the job summary and
annotations, which only ever read summary.warnings.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

test/refresh.test.ts

@@ -363,9 +363,15 @@ describe("robots", () => {
 
     expect(summary.outcomes[0]?.result).toBe("fetched");
     expect(summary.assumedRobots).toEqual(["game8.co"]);
-    expect(summary.warnings.some((w) => w.includes("--assume-robots-on-403"))).toBe(
-      true,
+    // Exactly one warning per host, and it carries the instruction. The host
+    // was reported twice for a while — once from here and once from a second
+    // loop in main() — which also left the run's "N warnings" count disagreeing
+    // with the number of lines printed under it.
+    const assumed = summary.warnings.filter((w) =>
+      w.includes("--assume-robots-on-403"),
     );
+    expect(assumed).toHaveLength(1);
+    expect(assumed[0]).toContain("Re-read it in a browser");
   });
 
   test("an ordinary run reports no assumed hosts at all", async () => {