chore: apply wbfy v21.0.2 conventions

AGENTS.md

@@ -19,7 +19,7 @@
 - After making changes, run locally only `bun run verify` (type checking and linting; up to 10 minutes) and the relevant tests; leave the full suite (`bun run verify-full`; up to 1 hour) to the PR's CI, or run it locally if PR CI does not. Fix errors, including CI failures, and re-run until they pass.
   - Run relevant tests with `bun wb test test/unit/example.test.ts --grep 'case name'` (omit `--grep` for the whole file). `bun wb verify --full <test-path> --grep 'case name'` combines verification with selected tests.
   - Wait for it to finish without restarting it: prefer completion notifications, otherwise the longest permitted wait; no output does not mean it has stopped. If the displayed excerpt is insufficient, read the indicated log file before rerunning. If the environment kills long-running commands, run them detached with a saved log and exit status.
-  - `verify` also prints `code-gauge` errors and warnings without failing. In code your change touches, fix every error, and each warning whose fix makes the code easier to read, with behavior-preserving changes (e.g., extract a helper, flatten branching, reuse the code it duplicates). Leave a violation whose only fix moves complexity elsewhere (e.g., splitting a function mechanically), restructures far more code than your change touches, or removes an intentional duplicate (e.g., a file mirroring another by design); allow each warning left with a `code-gauge-allow <metric> <max> -- <reason>` comment on its own line right above the start line reported for the function or duplicated block (`code-gauge-allow-file` for the whole file), where `<metric>` is the camelCase metric name (e.g., `functionParameterCount`) and `<max>` the reported value, and list each error left, which no comment can allow, with the reason, in the PR body's Notes, proposing a `code-gauge.config.json` exclusion there for an intentional duplicate. Never edit `code-gauge.config.json` to silence a violation unless asked. When a violation measures the code incorrectly (e.g., misparsed syntax, unrelated code reported as duplicated), search the issues of `WillBooster/code-gauge` and, if none covers it, create one with a freshly written minimal reproduction, the command, and its output.
+  - `verify` also prints `code-gauge` errors and warnings without failing. In code your change touches, fix every error, and each warning whose fix makes the code easier to read, with behavior-preserving changes (e.g., extract a helper, flatten branching, reuse the code it duplicates). Leave a violation whose only fix moves complexity elsewhere (e.g., splitting a function mechanically), restructures far more code than your change touches, or removes an intentional duplicate (e.g., a file mirroring another by design); allow each warning left with a `code-gauge-allow <metric> <max> -- <reason>` comment on its own line right above the function's reported start line; for a duplicated block, above the start line of its enclosing function, separately for each copy (`code-gauge-allow-file` for the whole file or a block outside a function), where `<metric>` is the camelCase metric name (e.g., `functionParameterCount`) and `<max>` the reported value, and list each error left, which no comment can allow, with the reason, in the PR body's Notes, proposing a `code-gauge.config.json` exclusion there for an intentional duplicate. Never edit `code-gauge.config.json` to silence a violation unless asked. When a violation measures the code incorrectly (e.g., misparsed syntax, unrelated code reported as duplicated), search the issues of `WillBooster/code-gauge` and, if none covers it, create one with a freshly written minimal reproduction, the command, and its output.
 - Once verified, commit and push to the current branch, and create a PR via `gh` if none exists for the branch.
   - Follow the Conventional Commits format (e.g., `feat:`, `fix:`).
   - End your commit message with a blank line followed by `Co-authored-by: WillBooster (AGENT_NAME) <agent@willbooster.com>`, replacing only `AGENT_NAME` with your agent name (e.g., `Claude Code`), the only AI attribution to add.

README.md

@@ -5,7 +5,7 @@
 [![Test](https://github.com/WillBooster/tree-sitter-markdown/actions/workflows/test.yml/badge.svg)](https://github.com/WillBooster/tree-sitter-markdown/actions/workflows/test.yml)
 [![Test rust](https://github.com/WillBooster/tree-sitter-markdown/actions/workflows/test-rust.yml/badge.svg)](https://github.com/WillBooster/tree-sitter-markdown/actions/workflows/test-rust.yml)
 [![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)
-[![wbfy](https://img.shields.io/badge/wbfy-20.51.1-1e90ff.svg)](https://github.com/WillBooster/shared/tree/main/packages/wbfy)
+[![wbfy](https://img.shields.io/badge/wbfy-21.0.2-1e90ff.svg)](https://github.com/WillBooster/shared/tree/main/packages/wbfy)
 [![crates.io](https://img.shields.io/crates/v/willbooster-tree-sitter-md.svg)](https://crates.io/crates/willbooster-tree-sitter-md)
 
 Markdown grammars for [tree-sitter](https://github.com/tree-sitter/tree-sitter), forked from

bunfig.toml

@@ -76,6 +76,7 @@ minimumReleaseAgeExcludes = [
   "code-gauge-linux-arm64-musl",
   "code-gauge-linux-x64-gnu",
   "code-gauge-linux-x64-musl",
+  "code-gauge-win32-x64-msvc",
   "commitkv",
   "gen-i18n-ts",
   "minimal-promise-pool",

package.json

@@ -53,7 +53,7 @@
     "@types/bun": "1.4.4",
     "@vitest/browser-playwright": "5.0.5",
     "@willbooster/oxlint-config": "1.4.9",
-    "@willbooster/wb": "22.32.3",
+    "@willbooster/wb": "23.0.0",
     "@willbooster/web-tree-sitter": "15.5.4",
     "conventional-changelog-conventionalcommits": "10.4.1",
     "lefthook": "2.2.2",