fix variants for toast

[Light2Dark]

📝 Summary

Code_mode would call toast with success kind, which is not supported at the moment. So, it would choose the wrong styles.

mo.status.toast(
    title="Claude reporting for duty! 🧑‍🍳",
    description="Ready to pair on the kitchen sink ✨ — what shall we cook up?",
    kind="success",  # <---- Not supported
)

This resolves to choose the default style and adds some better typing.

📋 Pre-Review Checklist

• For large changes, or changes that affect the public API: this change was discussed or approved through an issue, on Discord, or the community discussions (Please provide a link if applicable).
• Any AI generated code has been reviewed line-by-line by the human PR author, who stands by it.
• Video or media evidence is provided for any visual changes (optional).

✅ Merge Checklist

• I have read the contributor guidelines.
• Documentation has been updated where applicable, including docstrings for API changes.
• Tests have been added for the changes made.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
marimo-docs	Ready	Preview, Comment	Apr 16, 2026 6:03pm

[Copilot]

Pull request overview

Fixes toast styling selection by ensuring unsupported toast variant values (e.g. "success") fall back to the default toast styles instead of producing an unstyled/incorrect toast.

Changes:

• Extracted toast variant class definitions into a shared VARIANT_CLASSES constant and derived ToastVariant from it.
• Added a runtime isToastVariant guard and used it to resolve invalid variant values to "default" before passing into cva.

[Copilot]

isToastVariant uses value in VARIANT_CLASSES, which is true for inherited Object prototype keys (e.g. "toString"). That makes the type guard unsound and can result in non-string classNames being passed into cva (e.g. Object.prototype.toString), producing broken class output. Use an own-property check instead (e.g. Object.prototype.hasOwnProperty.call(VARIANT_CLASSES, value) or an equivalent safe helper).

Suggested change

	return typeof value === "string" && value in VARIANT_CLASSES;
	return (
	typeof value === "string" &&
	Object.prototype.hasOwnProperty.call(VARIANT_CLASSES, value)
	);

[kirangadhave]

We should do something like !!VARIANT_CLASSES[value]

[kirangadhave]

🚀 approving, but we should address the copilot suggestion

[kirangadhave]

We should do something like !!VARIANT_CLASSES[value]