Adds new plugin [zsaklak/kids-outfit-card]

[wroadd]

Checklist

• I've read the publishing documentation.
• I've added the HACS action to my repository.
• The actions are passing without any disabled checks in my repository.
• I've added a link to the action run on my repository below in the links section.
• I've created a new release of the repository after the validation actions were run successfully.

Links

Link to current release: https://github.com/zsaklak/kids-outfit-card/releases/tag/v0.1.1
Link to successful HACS action (without the ignore key): https://github.com/zsaklak/kids-outfit-card/actions/runs/34109288497
Link to successful hassfest action (if integration): Not applicable (Dashboard plugin).

Description

The integration-only hassfest checklist item is omitted because this is a Dashboard plugin.

Kids Outfit Card shows a consistent boy or girl character wearing the clothes recommended by the Kids Outfit integration. It is designed for children aged 4–12 to understand the outfit at a glance. Original SVG artwork changes clothing layers and accessories while preserving the character.

The dependency-free runtime bundle includes English and Hungarian, supports complete text overrides in any language, locale-aware formatting, RTL, a visual editor and a compact wall-tablet layout. The README includes rendered screenshots. Browser tests cover eight weather states, 390px layout, language selection, stale-data handling and escaping. The companion integration is submitted in #10729. I am the contributor under the zsaklak organization.

[hacs-bot]

Thank you for submitting your repository to HACS (Home Assistant Community Store).

Your submission is in the review queue:
Your repository is waiting to be reviewed and included in HACS.

You can view the current queue here. Pull requests are processed in the order they were created, oldest first.

What to avoid during review:
To help reviewers work efficiently, don't do the following:

• Comment on the pull request - The reviewer will contact you when they have feedback or questions.
• Open a new pull request - This won't speed up the process and creates duplicate work.
• Ask followers to comment on the pull request - This won't speed up the process and may delay your review.
• Merge in the default branch - Only do this if a maintainer asks you to resolve a merge conflict.

If you need to make changes:
You can continue updating your repository while waiting for review. Changes to your repository will be reflected when the reviewer examines it. Only comment on the pull request if you need to withdraw your submission or have critical information for reviewers.

About draft pull requests:
Draft pull requests aren't included in the review queue. Your pull request may be marked as draft by a reviewer if issues need to be addressed. Once you've resolved all issues, mark it as ready for review to re-enter the queue.

What happens next:
Once a reviewer examines your submission, they'll either:

• Approve and merge your pull request if everything meets the requirements
• Request changes or ask questions if adjustments are needed