[exKAZUu]

Why

Align repository configuration with wbfy v21.3.0.

Requirements

• required: Get PR chore: apply wbfy v21.3.0 #89 reviewed and ready to merge using review-booster followed by complete-pr.
• required: Work on the wbfy branch and push fixes normally; never force push.
• required: Align the repository with wbfy's conventions without hand-editing wbfy-managed generated files.
• required: Leave the pull request open and unmerged for the calling CLI.

Customer Summary

Issue templates no longer assign type labels. The editor API is unchanged.

Technical Summary

Apply wbfy's issue-template, release-label, and agent-instruction conventions; update the wbfy badge to v21.3.0 and @willbooster/wb to 23.0.2 with its lockfile entry. The release-label settings align with wbfy's generated configuration; the existing disabled success and failure notifications already prevent label assignment.

Testing

• review-booster completed with seven successful reviewers; its one minor finding about this description was corrected.
• Reproduced the release plugin's success and failure paths with both base and head configurations: neither assigns labels.
• complete-pr readiness check returned PASS at dc8b2c5. All five GitHub checks passed, including test / test and semantic-pr / semantic-pr.
• No repository files were changed during review, so no additional local suite was run.

Notes

Gemini's separate automatic review was unavailable because of its daily quota. The review-booster run completed with all seven reviewers successful; its completion head was reviewed by at least one successful exploration session, with full coverage unverified.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!