v2.3.1

fix(composer): resolve autoloader class collision with other Bonsai plugins

• Both this plugin and bonsai-code-injector shipped byte-identical composer.json files,
  causing Composer to generate the same ComposerAutoloaderInit{hash} class in both —
  fatal error when both plugins were active on the same site (reported on faranitaylor.com)
• Added a unique "name" field to composer.json and regenerated vendor/ from a clean install
• Bumped to 2.3.1

v2.3.0

2.3.0 - 2026-07-23
Added

[cookie-consent-video-embed-CookieScript.php] "Consent manager" setting (CookieScript / Cookiebot) so one plugin install can support either platform on a per-site basis.
[assets/js/ccve-cookiescript.js] Blocking attributes now switch at runtime: data-src/data-cookiecategory for CookieScript, data-cookieblock-src/data-cookieconsent for Cookiebot.
[assets/js/ccve-cookiescript.js] openCookiebotSettings() calling Cookiebot.renew(); the fallback CTA now routes to the correct manager's reopen call based on the setting, with a same-page fallback to the other manager's API if the primary one isn't present.

Changed

[cookie-consent-video-embed-CookieScript.php] Admin page title, header, and field descriptions generalised — no longer assume CookieScript is the only supported platform.
[readme.txt] Description, features list, and FAQ updated for dual consent-manager support; Stable tag synced to 2.3.0.

Fixed issues

V2

Update update checker to use new scheduling method for interval setting

Bonsai Cookie Consent

Add PucReadmeParser class for parsing plugin readme files

This commit introduces the PucReadmeParser class, which is a modified version of the WordPress Plugin Readme Parser. It utilizes Parsedown for Markdown parsing and includes methods for extracting various metadata from readme files, such as plugin name, description, requirements, tags, contributors, and more. The class also handles sanitization and filtering of text to ensure safe output.