[exKAZUu]

Why

Apply the repository conventions from @willbooster/wbfy v21.3.0.

Requirements

• required: Apply @willbooster/wbfy v21.3.0 repository configuration and get this PR reviewed and ready to merge.
• required: Keep fixes on the wbfy branch and push normally, without force pushes.
• required: Align the repository with wbfy's conventions without hand-editing wbfy-managed generated files.
• required: Leave this PR open and unmerged for the calling CLI.
• chosen: Retain the generated Cargo configuration and stable toolchain, explicitly disclose that Cargo 1.99.1 ignores the age setting, and defer enforcement to WillBooster/shared#1587. cargo metadata --locked --format-version 1 --no-deps reproduces the warning; upstream issue WillBooster/shared#1256 records stable support as blocked until Rust 1.100. Hand-editing generated output violates the request, and switching to nightly would broaden the toolchain contract solely for this setting.

Customer Summary

Adds Cargo's minimum publish age configuration; the pinned stable Cargo currently ignores it and prints a warning, so dependency age enforcement is unchanged.

Technical Summary

Set registry.global-min-publish-age = "7 days" in generated Cargo configuration and update the README's wbfy version badge.

Testing

The pre-push check passed. cargo metadata --locked --format-version 1 --no-deps succeeded and reproduced the ignored-setting warning. All five review-booster reviewers completed successfully; the PR description finding was fixed and the generator limitation was deferred upstream. complete-pr readiness returned PASS for commit 15b41e80f857b396cba2056af62da36729bd0858: all head checks passed, the PR is mergeable, and no review thread awaits a decision.

Notes

Cargo age enforcement requires toolchain support absent from the pinned stable version. The generator compatibility issue is tracked in WillBooster/shared#1587; generated files are retained unchanged.