commit 42dae8257e74cf30eb56384371b613a59932b20a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Sep 2 23:13:34 2026 +0200

sci-ml/unsloth-desktop: drop 0.1.801_beta 0.1.803_beta

Down to the last two, dropping each version's system-backend patch with
it since the patch is named per-version and nothing else references it.
Nothing in the tree depends on this package.

commit 78b5b8fa1743d90252d21e72c43ec11b29e7b2b1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Sep 2 23:13:16 2026 +0200

sci-ml/unsloth-desktop: add 0.1.806_beta

CRATES regenerated from the release Cargo.lock and diffed against
0.1.804: 671 registry crates either way, three of which moved --
log 0.4.33 -> 0.4.34, open 5.4.0 -> 5.4.1, reqwest 0.13.2 -> 0.13.4.
No crate added or removed, so the dependent-crate LICENSE block stands.
The one git-sourced crate, fix-path-env, is still the same commit, so
GIT_CRATES is unchanged. rust-version is still 1.89, matching
RUST_MIN_VER.

src_prepare's placeholder rewrite was re-checked rather than assumed:
upstream still ships version = "2026.4.8" in both src-tauri/Cargo.toml
and the unsloth-studio stanza of Cargo.lock, so the sed still matches.
Had the placeholder moved, the sed would have silently no-opped and the
app would have reported the wrong version with || die catching nothing.

system-backend.patch regenerated against this tree rather than copied,
so its line numbers are honest; the change content is identical to the
0.1.804 patch. verified 2026-09-02

commit 992a54651619fc9f235e56aa4d303e78140c57e0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Aug 27 19:10:58 2026 +0200

sci-ml/unsloth-desktop: add 0.1.804_beta

Effectively a pure copy: studio/src-tauri/Cargo.lock and Cargo.toml are
byte-identical to 0.1.803_beta, so the vendored CRATES list (671 registry
crates) carries over untouched, the lone git crate fix-path-env still
resolves to c4c45d5, and Cargo.toml still holds the 2026.4.8 placeholder
that src_prepare rewrites to the release version.

PATCHES references $-system-backend.patch, so the bump still needs a
version-named copy of the patch or src_prepare dies. process.rs and
desktop_backend_owner.rs did change upstream, but only cosmetically (a
Studio -> Unsloth rename in strings and comments, no lines added or
removed), and none of it lands near a patch site -- the 0.1.803 hunks apply
at identical offsets, so the patch content is copied unchanged under the
new name.

commit 6a71f865d90edc38bfe57cc97664cebd496cd8bf
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Aug 26 21:10:00 2026 +0200

sci-ml/unsloth-desktop: add 0.1.803_beta

PATCHES references $-system-backend.patch, so this bump needs a
version-named copy of the patch -- without it src_prepare dies. The 0.1.801
hunks apply to the 0.1.803 tree unchanged (identical context, line offsets
only), so the patch content is a straight copy under the new name.

The vendored CRATES list is byte-identical to 0.1.801 (671 registry
crates), the fix-path-env git crate still resolves to c4c45d5, and
Cargo.toml still carries the 2026.4.8 placeholder that src_prepare rewrites
to the release version.

commit d9f1d5ccc7017cd7d083bae6b897ebb82ab490fb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 24 11:57:22 2026 +0200

sci-ml/unsloth-desktop: new package, add 0.1.801_beta

From-source build of the Unsloth Studio desktop shell: a Tauri (Rust + webkit)
app that drives the sci-ml/unsloth[studio] Python backend. Built from the GitHub
release tag with CRATES vendored from Cargo.lock. Upstream ships a placeholder
Cargo version (2026.4.8) that its release CI rewrites before building, so
src_prepare stamps it to the packaged release and the app reports 0.1.801-beta.

A system-backend patch makes the shell prefer /usr/bin/unsloth and set
UNSLOTH_STUDIO_SYSTEM, so it drives the system sci-ml/unsloth[studio] backend
in-process instead of running install.sh and managing a ~/.unsloth/studio venv.

LICENSE declares the AGPL-3 studio app and its bundled OFL-1.1 @fontsource web
fonts; the proprietary Hellix font is stripped from the frontend dist before the
shell embeds it (the UI falls back to a system font for that text).