perf remove window load

[ptesei]

Note

Low Risk
Low risk: front-end timing change is localized to FAQ accordion init; bump script only affects maintainer release tooling, not runtime site behavior.

Overview
Front-end FAQ accordions no longer wait for the full window load event (images, late assets). Initialization runs in an init() helper on DOMContentLoaded when the document is still loading, or immediately if the DOM is already ready—so interactive FAQ UI should appear sooner on the page.

Release workflow: Adds bin/bump-version.js and npm run bump -- <patch|minor|major|x.y.z> to bump semver consistently across .plugin-data, package.json, lockfile, block block.json files, blockparty-faq.php, readme.txt, CHANGELOG.md, and README.md (with dated TBD changelog stubs). /bin is excluded from distribution via .distignore and .gitattributes, and the README documents the new script.

^{Reviewed by Cursor Bugbot for commit 8680969. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8680969. Configure here.}

[cursor]

Missing changelog link refs

Medium Severity

updateChangelogMd inserts a Keep a Changelog heading like ## [x.y.z] but never adds the matching footer reference link that CHANGELOG.md already maintains for every prior release, so new version headings render as unresolved references.

 

^{Reviewed by Cursor Bugbot for commit 8680969. Configure here.}

[cursor]

README changelog order broken

Low Severity

updateReadmeMd always prepends the new entry under ## Changelog, but README.md currently lists versions oldest-first. Each bump therefore places the newest release above 1.0.0 and out of sequence with the existing history.

 

^{Reviewed by Cursor Bugbot for commit 8680969. Configure here.}