v0.23.0

fxcss 0.23.0 lets fxcss try test a theme from a folder on your computer or from a private repository, and explains failures instead of printing a traceback.

• fxcss try ~/src/my-theme test-drives a local theme folder in a throwaway profile, the same way install already accepted folders. --ref and --commit choose GitHub versions, so with a folder they are ignored and say so.
• Private repositories work when you are signed in with gh auth login, or when GITHUB_TOKEN or GH_TOKEN is set. fxcss asks gh for a token only after an anonymous lookup finds nothing, so public themes need no sign-in.
• A missing repository, a private one you can't read, no network, a rejected token or a GitHub rate limit now prints a short explanation and exits with status 2. The explanation names the repository URL to check, where the token came from, and how to pass a folder instead.
• The fxcss.com website moved to its own website branch, which has its own build and deploy commands. main now holds only fxcss itself.
• Profile and variant documentation is clearer.

Upgrade an existing installation with pipx upgrade fxcss, or use pip install "fxcss[images]==0.23.0" in a virtual environment or CI.

Existing generated workflows keep their version pins until regenerated. Run fxcss init with your existing options and --force, then review the diff to keep local edits.

Full changes since v0.22.1.

The release workflow passed all 26 jobs, including cross-platform browser tests, installed-package checks and the PyPI installability gate.

A fresh installation from PyPI showed version 0.23.0. It explained a missing repository with exit status 2 and no traceback, rejected a missing folder, and found a theme in a local folder without launching Firefox. The published wheel and source archive have the same SHA256 hashes as the files the release workflow built and tested.