Docs: Update to jekyll-theme-amethyst 2.8.2

https://github.com/qunitjs/jekyll-theme-amethyst/commits/v2.8.2/

* Add scroll-based highlighting of "current" heading to the TOC.
* Expand at most one sidebar group for the current page.
* Add help cursor to `abbr` elements.

Author: Krinkle

docs/Gemfile

@@ -2,4 +2,4 @@ source "https://rubygems.org"
 ruby RUBY_VERSION
 
 # To apply changes, run `bundle update`.
-gem "jekyll-theme-amethyst", "2.7.2", group: :jekyll_plugins
+gem "jekyll-theme-amethyst", "2.8.2", group: :jekyll_plugins

docs/api/QUnit/module.md

@@ -220,7 +220,7 @@ QUnit.module('Database connection', {
 
 ### Hooks on nested modules
 
-_Back to [§ Hook order](#hook-order)._
+_See also [§ Hook order](#hook-order)._
 
 ```js
 QUnit.module('My Group', hooks => {

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](../callbacks/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.