[dermatz]

Summary

#267 was merged as a plain merge commit and its commits start with an emoji, so Release Please could not parse them and the Tailwind CSS v4 readiness check is missing from the release PR (#250). The workflow log shows commit could not be parsed for all of them.

This PR makes that feature appear in the changelog. Its title follows Conventional Commits, so it needs to be squash-merged.

The Tailwind CSS v4 readiness check was added to mageforge:hyva:compatibility:check in #267 and runs automatically when Hyvä is installed via Composer (--tailwind4 forces it).

Changes

• README: mention the Tailwind CSS v4 readiness check under the Hyvä commands
• Commands reference: update the overview row of compatibility:check

Documentation only, no code changes.

[Copilot]

🟢 Approval recommended

There are no active review issues for this documentation-only update highlighting the existing Tailwind CSS v4 readiness check.

No open issues 🎉

What changed in this PR

This documentation-only PR highlights the existing Tailwind CSS v4 readiness check in MageForge’s Hyvä command documentation. Its Conventional Commits title is intended to include the feature in the release changelog when squash-merged.

Changes:

• Mention the readiness check in the README’s Hyvä commands list.
• Update the command reference overview to include Tailwind CSS v4 compatibility.

File	Description
README.md	Highlights the readiness check under Hyvä commands.
docs/​commands_reference.md	Expands the compatibility command’s overview description.

_{Review effort: Balanced}