Docs: Fix various bad links

Once again, thanks to hydra-link-checker in our spider-check CI job!

Author: Krinkle

build/hydra-config.json

@@ -1,16 +1,18 @@
 {
   "//": [
-    "twitter.com serves broken redirect-loop",
-    "element.io and gitter.im chat rooms render fine but oddly use HTTP 404",
-    "npmjs.com responds HTTP 429 Too Many Requests too easily",
-    "Skip trivial github.com links to hopefully avoid HTTP 429 Too Many Requests",
+    "2023-05: twitter.com serves broken redirect-loop",
+    "2024-06: npmjs.com responds HTTP 429 Too Many Requests too easily",
+    "2024-07: element.io and gitter.im chat rooms render fine but oddly use HTTP 404",
+    "2025-01: github.com responds HTTP 429 Too Many Requests for the bulk of trivial links. We can probably keep a few other GitHub links.",
+    "2025-03: codepen.io (via Cloudflare) blocks hydra-link-checker with HTTP 403"
     ""
   ],
   "exclude_scheme_prefixes": [
     "https://twitter.com/",
     "https://app.element.io/",
     "https://app.gitter.im/",
     "https://www.npmjs.com/package/",
+    "https://codepen.io/",
     "https://github.com/qunitjs/qunit/issues/",
     "https://github.com/qunitjs/qunit/pull/",
     "https://github.com/qunitjs/qunit/blob/main/docs/_posts/"

docs/api/reporters/perf.md

@@ -50,7 +50,7 @@ QUnit.reporters.perf.init(QUnit);
 
 **Note:** As of 2025, the [Node.js inspector](https://nodejs.org/docs/latest/api/debugger.html#v8-inspector-integration-for-nodejs) does not yet send User Timing measures to Chrome DevTools ([upstream nodejs/node#47813](https://github.com/nodejs/node/issues/47813)).
 
-This means that you _can_ retrieve the QUnit measures from [`performance.getEntries()`](https://nodejs.org/docs/latest/api/perf_hooks.html) and export or visualise them with tooling of your own (e.g. from a [runEnd event](../callback/QUnit.on.md##the-runend-event), or via a PerformanceObserver).
+This means that you _can_ retrieve the QUnit measures from [`performance.getEntries()`](https://nodejs.org/docs/latest/api/perf_hooks.html) and export or visualise them with tooling of your own (e.g. from a [runEnd event](../callbacks/QUnit.on.md##the-runend-event), or via a PerformanceObserver).
 
 But, when connecting Chrome DevTools to a Node.js process, these are not currently visualised. If you currently test frontend code for browsers via jsdom in Node.js, consider [testing in a real browser](../../browser.md) instead.
 

docs/intro.md

@@ -26,7 +26,7 @@ Check these QUnit tutorials and examples, to make the most of your unit tests!
 1. [Assertions](./api/assert/index.md): Partial object comparison, expected exceptions, and much more.
 1. [Browser](./browser.md): Productivity tricks, Browser automation, What can the toolbar do?
 1. [CLI](./cli.md): Productivity tricks, Code coverage.
-1. [Reporter API](./callbacks/QUnit.on.md#reporter-api): Event emitter, Create your own reporter.
+1. [Reporter API](./api/callbacks/QUnit.on.md#reporter-api): Event emitter, Create your own reporter.
 1. [Theme API](./browser.md#theme-api): Create your own theme.
 
 ## Support