docs: list actual upstream PRs (#13372, #13719, #13315) + KX matching patches

README.md

@@ -17,17 +17,31 @@ in-progress PRs improving Kobra X support — recommended for use with [KX-Bridg
 
 ## What's inside
 
-Standard OrcaSlicer (v2.4.0-dev) with these **additional PRs from SoftFever/OrcaSlicer**
-applied on top:
+Standard OrcaSlicer (v2.4.0-alpha) with three upstream PRs and four KX-specific
+matching improvements applied on top.
 
-- **[PR #13372](https://github.com/SoftFever/OrcaSlicer/pull/13372)** — Moonraker Happy Hare AMS Sync Fix
-  (filament sync now keeps the slot positions intact even with empty slots)
-- **[PR #13529](https://github.com/SoftFever/OrcaSlicer/pull/13529)** — Anycubic Kobra X full printer profile
-- **[PR #13677](https://github.com/SoftFever/OrcaSlicer/pull/13677)** — Kobra X multicolor G-code fix
+**Upstream PRs from SoftFever/OrcaSlicer:**
 
-For most users the AMS-related fix (#13372) is the practical reason to use this
-build over upstream OrcaSlicer: with an empty slot in the middle of the AMS,
-upstream shifts the colors onto the wrong positions during filament sync.
+- **[PR #13372](https://github.com/SoftFever/OrcaSlicer/pull/13372)** — Moonraker Happy Hare AMS sync fix
+  (filament sync keeps slot positions intact even with empty slots)
+- **[PR #13719](https://github.com/SoftFever/OrcaSlicer/pull/13719)** — Vendor + Name matching for Moonraker
+  (reads `name` + `vendor_name` per slot and matches against the user's filament presets), by [@LordGuenni](https://github.com/LordGuenni)
+- **[PR #13315](https://github.com/SoftFever/OrcaSlicer/pull/13315)** — Unique `filament_id` for user presets
+  (newly created custom profiles get a fresh ID instead of inheriting `OGFL99` from the generic parent), by [@mrnoisytiger](https://github.com/mrnoisytiger)
+
+**KX-specific patches on top of the PRs:**
+
+- Respect the bridge filament hint (`tray_info_idx` + vendor)
+- Vendor match also when the chosen base preset is **not is_compatible** with the active printer (so a profile copied from a different machine still matches by vendor)
+- Vendor match when `tray_info_idx` is set but its preset is incompatible
+- Two-pass lookup: first compatible presets, then all visible ones
+
+**Why this matters for KX-Bridge users:** the bridge already sends concrete brand
+info per AMS slot (`name + vendor_name + gate_filament_name`). Without
+PR #13719 stock OrcaSlicer ignores that and falls back to `Generic PLA` for every
+slot. With the KX build OrcaSlicer matches your real user presets — including
+custom profiles you imported into the bridge via the [Import own OrcaSlicer
+profiles](https://gitea.it-drui.de/viewit/KX-Bridge-Release#-features) flow.
 
 ---
 
@@ -35,12 +49,12 @@ upstream shifts the colors onto the wrong positions during filament sync.
 
 Get the latest binaries from the [Releases page](https://gitea.it-drui.de/viewit/OrcaSlicer-KX/releases):
 
-- **Linux:** `OrcaSlicer_Linux_V2.4.0-dev.AppImage` — `chmod +x` and run.
-- **Windows:** `OrcaSlicer-Windows-x64.zip` — extract and run `OrcaSlicer.exe`.
+- **Linux:** `OrcaSlicer_Linux_V2.4.0-alpha.AppImage` — `chmod +x` and run.
+- **Windows:** `OrcaSlicer-Windows-x64.zip` — extract and run `orca-slicer.exe`.
 
 Checksums in `SHA256SUMS.txt`. macOS is not provided here — build from upstream.
 
-> ⚠ This is a **pre-release dev build** (OrcaSlicer 2.4.0-dev). Use at your own risk.
+> ⚠ This is an **alpha build** (OrcaSlicer 2.4.0-alpha). Use at your own risk.
 > For a stable release, use upstream OrcaSlicer.
 
 ---
@@ -58,23 +72,8 @@ separate so licenses, source provenance and update cycles don't get tangled.
 
 These builds are derivatives of [OrcaSlicer](https://github.com/SoftFever/OrcaSlicer),
 licensed under **GNU AGPL-3.0**. All rights to the upstream OrcaSlicer code and to
-the linked PRs remain with their respective authors. Sources are available via:
+the contributing PRs belong to their respective authors.
 
-- Upstream: <https://github.com/SoftFever/OrcaSlicer>
-- The three additional PRs linked above (#13372 / #13529 / #13677)
-
-No upstream code is mirrored in this repo — this repo only hosts the built
-binaries. If you need the exact source state used for a build, take upstream
-OrcaSlicer at the build's commit and apply the listed PRs.
-
----
-
-## Rebuild workflow
-
-When upstream or one of the PRs changes:
-
-1. In a clean OrcaSlicer checkout: rebase on `SoftFever/OrcaSlicer:main`,
-   cherry-pick or merge the three PR branches.
-2. Build Linux AppImage and Windows ZIP.
-3. New release tag `v<upstream-version>-kx<N>` (e.g. `v2.4.1-kx1`).
-4. Re-upload assets with `SHA256SUMS.txt`.
+The KX-specific matching patches on top of the PRs live alongside the OrcaSlicer
+source tree used to build these binaries; reach out via the Gitea issues if you
+want the exact patch series.