chore: apply wbfy v21.2.0 repository conventions

.github/ISSUE_TEMPLATE/bug.md

@@ -2,7 +2,6 @@
 name: Bug / Problem
 about: Something behaves wrongly
 title: 'fix: '
-labels: 't: fix :bug:'
 ---
 
 <!-- Keep Problem and Proposal; delete Evidence or Impact when they add nothing. Write in English, except text whose language is part of what the code handles (e.g., UI strings, test inputs). Delete these comments. -->

.github/ISSUE_TEMPLATE/change.md

@@ -2,7 +2,6 @@
 name: Change / Feature
 about: Propose a change that a third party could implement without asking a question
 title: 'feat: '
-labels: 't: feat :sparkles:'
 ---
 
 <!-- Keep the first three sections for any change and add the others as the change grows; a large change fills all of them (spec-booster reviews against this list). Write in English, except text whose language is part of what the code handles (e.g., UI strings, test inputs). Delete these comments. -->

.review-fix-loop.jsonc

@@ -0,0 +1,8 @@
+{
+  "rflAgent": {
+    "custom": {
+      "baseUrl": "https://llm.willbooster.com/v1",
+      "apiKeyCommand": "bunx @willbooster-private/llm-proxy token",
+    },
+  },
+}

AGENTS.md

@@ -32,8 +32,8 @@
   - Never drop or weaken a `required` line to fit what was implemented: when one cannot hold in the diff, keep it and say so in Notes.
 - When creating an issue:
   - Follow the closest template under `.github/ISSUE_TEMPLATE/`: `bug.md` for wrong behavior, `change.md` for anything to build or alter; a question or note fitting neither, or a repository without templates, needs no template.
-  - Title: a Conventional Commits prefix for the type that fits the change (`feat:`, `fix:`, `refactor:`, `docs:`, `chore:`, ...); when it differs from the template's `title` prefix, replace the template's type label (`t: ...`) with the one matching the type.
-  - The YAML front matter between the `---` lines is metadata, not body text: pass its `labels` via `--label` and submit only the content below the closing `---` as the body.
+  - Title: a Conventional Commits prefix for the type that fits the change (`feat:`, `fix:`, `refactor:`, `docs:`, `chore:`, ...).
+  - The YAML front matter between the `---` lines is metadata, not body text: submit only the content below the closing `---` as the body.
 - In any explanatory text (commit messages, PR descriptions, documentation, code comments, etc.) other than the PR body's Requirements section, describe only the current implementation: drop any statement naming an identifier, feature, or concept you cannot confirm exists in the final diff or the current codebase (e.g., one added and later removed or renamed along the way). Whenever documentation or comments no longer match the current implementation, delete or rewrite them, even in files you are not otherwise changing. Mention a past state only where it is needed to understand why the current design is as it is, or when explicitly asked; files that record history by design (e.g., a changelog) are exempt.
 - Use heredoc for multi-line command input (e.g., `git commit -F -`, `gh pr create --body-file -`, `gh issue create --body-file -`).
 - Put temporary files in `.tmp`; use `/tmp` only for files that must live outside the repo.

README.md

@@ -5,7 +5,7 @@
 [![Test](https://github.com/WillBooster/tree-sitter-go/actions/workflows/test.yml/badge.svg)](https://github.com/WillBooster/tree-sitter-go/actions/workflows/test.yml)
 [![Test rust](https://github.com/WillBooster/tree-sitter-go/actions/workflows/test-rust.yml/badge.svg)](https://github.com/WillBooster/tree-sitter-go/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-21.0.2-1e90ff.svg)](https://github.com/WillBooster/shared/tree/main/packages/wbfy)
+[![wbfy](https://img.shields.io/badge/wbfy-21.2.0-1e90ff.svg)](https://github.com/WillBooster/shared/tree/main/packages/wbfy)
 [![crates.io](https://img.shields.io/crates/v/willbooster-tree-sitter-go.svg)](https://crates.io/crates/willbooster-tree-sitter-go)
 
 Go grammar for [tree-sitter](https://github.com/tree-sitter/tree-sitter), forked from