Fix dangling links in docs

[ci skip]

Author: dahlia

.github/workflows/build.yaml

@@ -260,12 +260,14 @@ jobs:
           EXTRA_NAV_TEXT=Unstable \
           EXTRA_NAV_LINK="$UNSTABLE_DOCS_URL" \
           SITEMAP_HOSTNAME="$STABLE_DOCS_URL" \
+          JSR_REF_VERSION=stable \
           bun run build
         else
           bun add -Df --no-cache @fedify/fedify@dev
           EXTRA_NAV_TEXT=Stable \
           EXTRA_NAV_LINK="$STABLE_DOCS_URL" \
           SITEMAP_HOSTNAME="$UNSTABLE_DOCS_URL" \
+          JSR_REF_VERSION=unstable \
           bun run build
         fi
       env:

docs/.vitepress/config.mts

@@ -14,7 +14,7 @@ import { withMermaid } from "vitepress-plugin-mermaid";
 
 const jsrRefPlugin = await jsrRef({
   package: "@fedify/fedify",
-  version: "unstable",
+  version: process.env.JSR_REF_VERSION ?? "unstable",
   cachePath: ".jsr-cache.json",
 });
 

docs/manual/inbox.md

@@ -121,7 +121,7 @@ collection objects.  In such cases, you may need to recursively resolve the
 collection objects to determine the recipients of the activity:
 
 ~~~~ typescript twoslash
-import { 
+import {
   Collection,
   Create,
   type InboxListenerSetters,
@@ -431,8 +431,7 @@ federation.setInboxListeners("/{identifier}/inbox", "/inbox")
 > probably won't trust the forwarded activity.[^2]
 >
 > If you don't want to forward unsigned activities, you can turn on
-> the `~ForwardActivityOptions.skipIfUnsigned` option in
-> the `~InboxContext.forwardActivity()` method:
+> the `skipIfUnsigned` option in the `~InboxContext.forwardActivity()` method:
 >
 > ~~~~ typescript twoslash
 > import { type InboxContext } from "@fedify/fedify";
@@ -447,7 +446,7 @@ federation.setInboxListeners("/{identifier}/inbox", "/inbox")
 
 > [!NOTE]
 > The `~InboxContext.forwardActivity()` method does not use a [two-stage
-> delivery process](./send.md#optimizing-activity-delivery-for-large-audiences), 
+> delivery process](./send.md#optimizing-activity-delivery-for-large-audiences),
 > because `~InboxContext.forwardActivity()` method is invoked inside inbox
 > listeners, which are usually running in the background task worker.
 

docs/manual/mq.md

@@ -256,7 +256,7 @@ Handle the `~MessageQueueEnqueueOptions.delay` option if provided in
 `MessageQueueEnqueueOptions`.  Ensure the method is non-blocking
 (use async operations where necessary).
 
-### Implement `~MessageQueue.enqueueMany()` method (optional)
+### Implement `~MessageQueue.enqueueMany` method (optional)
 
 *This API is available since Fedify 1.5.0.*