FlxKeys CONTROL vs. WINDOWS vs. CTRL vs. COMMAND (vs. META?)

On Mac, there is SEEMINGLY no key for the COMMAND key... after some investigation, it seems to be the same keycode as the FlxKeys.WINDOWS keycode, which is 15.

Digging a bit further, the OpenFL class KeyboardEvent has some interesting bools available

       /**
		Indicates whether the Command key is active (`true`) or inactive
		(`false`). Supported for Mac OS only. On Mac OS, the `commandKey`
		property has the same value as the `ctrlKey` property.
	**/
	public var commandKey:Bool;

	/**
		Indicates whether the Control key is active (`true`) or inactive
		(`false`). On Windows and Linux, this is also true when the Ctrl key
		is active.
	**/
	public var controlKey:Bool;

	/**
		On Windows and Linux, indicates whether the Ctrl key is active
		(`true`) or inactive(`false`); On Mac OS, indicates
		whether either the Ctrl key or the Command key is active.
	**/
	public var ctrlKey:Bool;

I'm wondering if there's a nice way to incorporate cleanly a way to get COMMAND off Mac, without some fussyness from trying to just use FlxKeys.WINDOWS.

Thoughts/ideas

1. Renaming FlxKeys.WINDOWS to something like FlxKeys.META, and having a proper comment around it describing that it's Windows key on Windows, and the COMMAND key on Mac
2. Incorporating something around KeyboardEvent.ctrlKey, in cases where you might want to use CTRL on Windows, AND have it sorta "auto" use COMMAND on Mac. Something like having both FlxKey.CONTROL for when you want CTRL on Win, and CONTROL on mac, AND THEN having FlxKey.CTRL for when you want to have CTRL on Win, and then uses COMMAND on mac.
3. Having a FlxKey.COMMAND, that only is true/properly resolves on Mac, and when compiled to windows, doesn't return?

Start with the FlxKeys definitions and the referenced OpenFL KeyboardEvent properties. Compare how CONTROL, WINDOWS, CTRL, COMMAND, and META should behave across Mac, Windows, and Linux, then check existing keyboard-input usage. Done means the project has an agreed cross-platform API and corresponding documented behavior.