Apply Hongdown formatter to Markdown files

Add Hongdown as a dev dependency and apply consistent formatting
across all Markdown documentation:

- Standardize numbered list format (1.  with two spaces)
- Sort reference links alphabetically
- Add blank lines between bullet points for readability
- Fix missing code fence closures in docs/concepts/events.md
  and docs/concepts/message.md
- Correct duplicate numbering in docs/deploy/self-hosting.md
- Normalize nested list indentation in CHANGES.md
- Add hongdown-disable comments for VitePress special syntax

Author: dahlia

.hongdown.toml

@@ -0,0 +1,2 @@
+include = ["*.md", "**/*.md"]
+exclude = ["**/node_modules/**", "**/dist/**", "**/.git/**"]

AGENTS.md

@@ -93,8 +93,8 @@ Architecture
 ### Build system
 
  -  Uses *tsdown* for cross-platform builds (Deno -> Node.js/npm)
- -  Generates ESM (*dist/*.js*) and CommonJS (*dist/*.cjs*) outputs
- -  Creates TypeScript definitions for both (*dist/*.d.ts*, *dist/*.d.cts*)
+ -  Generates ESM (_dist/\*.js_) and CommonJS (_dist/\*.cjs_) outputs
+ -  Creates TypeScript definitions for both (_dist/\*.d.ts_, _dist/\*.d.cts_)
  -  Includes Temporal polyfill injection for Node.js compatibility
 
 ### Dual runtime support
@@ -130,22 +130,25 @@ and Node.js compatibility.
 
 ### When making changes
 
- 1. Run `deno task check` before committing to validate all aspects
- 2. The build process (*tsdown*) generates dual outputs for both runtimes
- 3. Tests should work in both Deno and Node.js environments
- 4. *Update documentation*: New features must be documented in the *docs/*
+1.  Run `deno task check` before committing to validate all aspects
+2.  The build process (*tsdown*) generates dual outputs for both runtimes
+3.  Tests should work in both Deno and Node.js environments
+4.  *Update documentation*: New features must be documented in the *docs/*
     directory
- 5. *Update changelog*: Any user-facing changes must be recorded in
+5.  *Update changelog*: Any user-facing changes must be recorded in
     *CHANGES.md*
 
 ### Commit messages
 
  -  Do not use Conventional Commits (no `fix:`, `feat:`, etc. prefixes).
     Keep the first line under 50 characters when possible.
+
  -  Focus on *why* the change was made, not just *what* changed.
+
  -  When referencing issues or PRs, use permalink URLs instead of just
     numbers (e.g., `#123`).  This preserves context if the repository
     is moved later.
+
  -  When listing items after a colon, add a blank line after the colon:
 
     ~~~~
@@ -249,6 +252,7 @@ Code style
 
  -  All exported APIs must have JSDoc comments describing their purpose,
     parameters, and return values.
+
  -  For APIs added in a specific version, include the `@since` tag with the
     version number:
 
@@ -329,8 +333,8 @@ Code style
 
 ### Log messages
 
- -  This project uses [LogTape] for logging.  Refer to the [LogTape LLM
-    documentation] for detailed usage.
+ -  This project uses [LogTape] for logging.  Refer to the
+    [LogTape LLM documentation] for detailed usage.
 
  -  Use [structured logging] with LogTape instead of string interpolation:
 
@@ -429,7 +433,9 @@ documentation:
 ### Lists
 
  -  Use ` -  ` (space-hyphen-two spaces) for unordered list items
+
  -  Indent nested items with 4 spaces
+
  -  Align continuation text with the item content:
 
     ~~~~
@@ -441,6 +447,7 @@ documentation:
 ### Code blocks
 
  -  Use four tildes (`~~~~`) for code fences instead of backticks
+
  -  Always specify the language identifier:
 
     ~~~~~
@@ -461,6 +468,7 @@ documentation:
 
  -  Use reference-style links placed at the *end of each section*
     (not at document end)
+
  -  Format reference links with consistent spacing:
 
     ~~~~

CHANGES.md

@@ -123,6 +123,8 @@ Released on August 8, 2025.
     fix [CVE-2025-54888] that addresses an authentication bypass
     vulnerability allowing actor impersonation.  [[CVE-2025-54888]]
 
+[CVE-2025-54888]: https://github.com/fedify-dev/fedify/security/advisories/GHSA-6jcc-xgcr-q3h4
+
 
 Version 0.2.1
 -------------
@@ -145,7 +147,7 @@ Released on April 21, 2025.
  -  Added custom emoji support.
 
      -  The return type of `Text.getTags()` method became
-         `AsyncIterable<Link | Object>` (was `AsyncIterable<Link>`).
+        `AsyncIterable<Link | Object>` (was `AsyncIterable<Link>`).
      -  Added `Bot.addCustomEmojis()` method.
      -  Added `CustomEmojiText` class.
      -  Added `customEmoji()` function.
@@ -225,8 +227,6 @@ Released on August 8, 2025.
     fix [CVE-2025-54888] that addresses an authentication bypass
     vulnerability allowing actor impersonation.  [[CVE-2025-54888]]
 
-[CVE-2025-54888]: https://github.com/fedify-dev/fedify/security/advisories/GHSA-6jcc-xgcr-q3h4
-
 
 Version 0.1.1
 -------------

SECURITY.md

@@ -14,8 +14,8 @@ Reporting a vulnerability
 -------------------------
 
 If you think you have found a security issue, please *do not* open a public
-issue.  Instead, please open a private vulnerability report by [creating a new
-draft security advisory][1].
+issue.  Instead, please open a private vulnerability report by
+[creating a new draft security advisory][1].
 
 We will review your report and respond within 48 hours.
 

deno.json

@@ -1,12 +1,6 @@
 {
-  "workspace": [
-    "packages/*",
-    "examples/*"
-  ],
-  "unstable": [
-    "kv",
-    "temporal"
-  ],
+  "workspace": ["packages/*", "examples/*"],
+  "unstable": ["kv", "temporal"],
   "imports": {
     "@fedify/fedify": "jsr:@fedify/fedify@1.10.0",
     "@logtape/logtape": "jsr:@logtape/logtape@^1.3.5",
@@ -27,29 +21,21 @@
     "src/css"
   ],
   "fmt": {
-    "exclude": [
-      "*.md",
-      "*.yaml",
-      "*.yml"
-    ]
+    "exclude": ["*.md", "*.yaml", "*.yml"]
   },
   "tasks": {
+    "hongdown": "deno run -A npm:hongdown@^0.1.0-dev.37",
     "check": {
-      "dependencies": [
-        "check-versions"
-      ],
-      "command": "deno check && deno lint && deno fmt --check && deno publish --dry-run --allow-dirty"
+      "dependencies": ["check-versions"],
+      "command": "deno check && deno lint && deno fmt --check && deno task hongdown --check && deno publish --dry-run --allow-dirty"
     },
     "check-versions": "deno run --allow-read --allow-write scripts/check_versions.ts",
+    "fmt": "deno fmt && deno task hongdown --write",
     "install": "deno cache packages/*/src/*.ts && pnpm install",
     "test": "deno test --allow-read --allow-write --allow-env --allow-net=hollo.social --parallel",
     "test:node": "pnpm install && pnpm run -r test",
     "test-all": {
-      "dependencies": [
-        "check",
-        "test",
-        "test:node"
-      ]
+      "dependencies": ["check", "test", "test:node"]
     },
     "coverage": "deno task test --coverage --clean && deno coverage --html",
     "hooks:install": "deno run --allow-read=deno.json,.git/hooks/ --allow-write=.git/hooks/ jsr:@hongminhee/deno-task-hooks",

deno.lock

@@ -3,4 +3,5 @@ description: >-
   The changelog contains a list of changes made to BotKit.  It is useful for
   developers who want to know what has changed in the library.
 ---
+
 <!--@include: ../CHANGES.md-->

docs/changelog.md

@@ -68,11 +68,11 @@ On production, you probably want to use one of the following drivers:
 Or if you want to implement your own custom key–value store,
 [that is also possible!][2]
 
-[1]: https://fedify.dev/manual/kv
 [`MemoryKvStore`]: https://fedify.dev/manual/kv#memorykvstore
 [`DenoKvStore`]: https://fedify.dev/manual/kv#denokvstore-deno-only
 [`RedisKvStore`]: https://fedify.dev/manual/kv#rediskvstore
 [`PostgresKvStore`]: https://fedify.dev/manual/kv#postgreskvstore
+[1]: https://fedify.dev/manual/kv
 [2]: https://fedify.dev/manual/kv#implementing-a-custom-kvstore
 
 
@@ -219,11 +219,11 @@ Or if you want to implement your own custom message queue,
 > recommend to configure the `~CreateBotOptions.queue` to make your bot
 > performant and scalable.
 
-[3]: https://fedify.dev/manual/mq
 [`InProcessMessageQueue`]: https://fedify.dev/manual/mq#inprocessmessagequeue
 [`DenoKvMessageQueue`]: https://fedify.dev/manual/mq#denokvmessagequeue-deno-only
 [`RedisMessageQueue`]: https://fedify.dev/manual/mq#redismessagequeue
 [`PostgresMessageQueue`]: https://fedify.dev/manual/mq#postgresmessagequeue
+[3]: https://fedify.dev/manual/mq
 [4]: https://fedify.dev/manual/mq#implementing-a-custom-messagequeue
 
 ### `~CreateBotOptions.software`
@@ -243,7 +243,7 @@ It consists of the following properties:
     ~~~~ typescript twoslash
     // @noErrors: 2345
     import { createBot, parseSemVer } from "@fedify/botkit";
-
+    
     const bot = createBot<void>({
       // Omitted other options for brevity
       software: {
@@ -496,7 +496,7 @@ https://8eba96f5416581.lhr.life/
 Press ^C to close the tunnel.
 ~~~~
 
-[^1]: You need to install the `fedify` command first.  [There are multiple ways
+[^1]: You need to install the `fedify` command first. [There are multiple ways
       to install it.][5]
 [^2]: The hostname will be different in your case.
 

docs/concepts/bot.md

@@ -207,7 +207,7 @@ document.
 > bot.onReply = async (session, reply) => {
 >   await reply.reply(text`Thanks for your reply, ${reply.actor}!`);
 > };
->
+> 
 > bot.onMention = async (session, message) => {
 >   if (message.replyTarget == null) {  // [!code highlight]
 >     await message.reply(text`You called me, ${message.actor}?`);
@@ -225,12 +225,13 @@ document.
 > bot.onMention = async (session, message) => {
 >   await message.reply(text`You called me, ${message.actor}?`);
 > };
->
+> 
 > bot.onReply = async (session, reply) => {
 >   if (!reply.mentions.some(m => m.id?.href === session.actorId.href)) {
 >     await reply.reply(text`Thanks for your reply, ${reply.actor}!`);
 >   }
 > };
+> ~~~~
 
 
 Quote
@@ -306,7 +307,7 @@ bot.onMessage = async (session, message) => {
 > bot.onMention = async (session, message) => {
 >   await message.reply(text`You called me, ${message.actor}?`);
 > };
->
+> 
 > bot.onMessage = async (session, message) => {
 >   if (message.mentions.some(m => m.id?.href === session.actorId.href)) {
 >     return;