26c6c410e0e0.Current upstream support is not platform-parity
The Windows workflow documents a bundled decorative skin installed and launched through PowerShell. It does not currently document a macOS-equivalent command that accepts any wallpaper plus three colors. A wallpaper downloaded here is a design asset, not evidence that the Windows injector will consume it.
What you can use safely now
You can use the Builder to evaluate crop, palette, and readability, then keep the wallpaper and v2 recipe as portable data. If you run the upstream Windows skin, follow its own install, start, verify, and restore scripts. Never copy the macOS shell command into PowerShell or edit files inside WindowsApps.
How to recognize real future support
Look for an explicit upstream Windows parameter or documented theme-pack schema, tests that validate the imported image, and a restore path that removes only the matching injected state. Until those exist on the checked main commit, treat arbitrary-image Windows support as unverified.
Completion checklist
- Windows guide explicitly names the feature
- Package source is the original repository
- Verify script passes
- Restore script is available