Docs: the onebit recipe lives in our Lemonade fork

README.md

@@ -30,8 +30,9 @@ serves each model behind an OpenAI-compatible API (`1bit serve`), whatever devic
 
 > **Status:** the engine runs inside Lemonade through `1bit serve` ([docs/lemonade.md](docs/lemonade.md),
 > [docs/serve.md](docs/serve.md)); the NPU, Vulkan, HRX and ZINC each pass its end-to-end test on
-> Strix Halo, and the Lemonade recipe that runs it (`onebit`) passes Lemonade's own LLM test suite on
-> Vulkan and HRX and is being prepared for upstream. Following geramyL's review the engine no longer
+> Strix Halo, and the Lemonade recipe that runs it (`onebit`, in our fork
+> [1bit-MONSTER/lemonade](https://github.com/1bit-MONSTER/lemonade)) passes Lemonade's own LLM test
+> suite on Vulkan and HRX. Following geramyL's review the engine no longer
 > vendors Lemonade: Lemonade is the host, 1bit is the engine inside it. Ported so far: HRX + Vulkan in
 > one build on AMD's live ggml-hrx ([docs/hrx.md](docs/hrx.md)), the NPU engine on full ELFs with the
 > upstream XDNA stack pinned ([docs/npu.md](docs/npu.md); its layer kernel is not yet built from

docs/PORTING.md

@@ -21,7 +21,7 @@ Each step below is one PR (or a short series) that builds and runs on Strix Halo
 
 | Step | Component | Source in 1bit-MONSTER | Done when |
 |---|---|---|---|
-| 1 | **The engine runs inside Lemonade.** Lemonade runs `1bit serve` as a backend: one model per process behind an OpenAI-compatible API | `tools/unified_server.cpp` | **landed** ([docs/serve.md](serve.md)): NPU, Vulkan, HRX and ZINC pass `serve_e2e` on Strix Halo; `smoke_serve` runs in CI. The engine first embedded Lemonade (v11.9.0 plus local recipes); after geramyL's review it is embedded *into* Lemonade instead: the vendored copy is removed, and a Lemonade recipe that launches `1bit serve` is being prepared for upstream ([docs/lemonade.md](lemonade.md)) |
+| 1 | **The engine runs inside Lemonade.** Lemonade runs `1bit serve` as a backend: one model per process behind an OpenAI-compatible API | `tools/unified_server.cpp` | **landed** ([docs/serve.md](serve.md)): NPU, Vulkan, HRX and ZINC pass `serve_e2e` on Strix Halo; `smoke_serve` runs in CI. The engine first embedded Lemonade (v11.9.0 plus local recipes); after geramyL's review it is embedded *into* Lemonade instead: the vendored copy is removed, and the Lemonade recipe that runs `1bit serve` (`onebit`) lives in our fork [1bit-MONSTER/lemonade](https://github.com/1bit-MONSTER/lemonade) ([docs/lemonade.md](lemonade.md)) |
 | 2 | **HRX with Vulkan.** llama.cpp with `GGML_HRX=ON` and `GGML_VULKAN=ON` in one build, on AMD's tested pair | `1bit-MONSTER/llama.cpp` `1bit/hrx-vulkan` (AMD's `hrx-graph-develop-v2`) + `ROCm/hrx-system`, pinned from `ROCm/ggml-staging-automation` | **landed** ([docs/hrx.md](hrx.md)): `1bit serve` runs the same checkpoint on `Vulkan0` and `HRX0`; kept current by `bump-hrx.yml` |
 | 3 | **NPU engine.** Full ELFs only, and the open 16-tile layer kernel built from source | `engine/npu` (`npu_engine_universal.cpp`, `I8Ctx::init_elf`); ELF dispatch table on `backup/iso-build-elf-native-2026-09-22`; kernel on `bench/fastlane-16tile-corrections-2026-09-22` | **3a–3c landed** ([docs/npu.md](npu.md)). 3a (#8): full ELFs generated in C++, reproducing all 5,153 captured contexts. 3b/3c (#9): the lane runtime (logits bit-identical to the reference lane, 24/24 steps, 11.0 ms/token), tokenizer, `1bit unified`, and Qwen3-0.6B served on the NPU (now through `1bit serve`). The XDNA driver and XRT are pinned upstream and built privately (#12). **Open:** the layer kernel and lm-head artifacts are not yet built from source (npu.md, "Open") |
 | + | **Linux kernel.** The kernel that provides `amdxdna` and `amdgpu`, pinned to upstream | `torvalds/linux` release tags; config from the Strix Halo kernel of 2026-09-23 | **pinned** ([docs/kernel.md](kernel.md)): v7.3-rc4 builds into Debian packages with `amdxdna` in-tree; kept current by `bump-linux.yml`. Installing it on Strix Halo is a separate, deliberate step |

docs/lemonade.md

@@ -47,9 +47,24 @@ One recipe in Lemonade runs the engine, `onebit`, in the same shape as its
 Lemonade downloads and resolves GGUF checkpoints as for llamacpp, and its
 backend selector picks the device (`vulkan`, `hrx`, `npu`, or `cuda` through
 ZINC). Replies already carry Lemonade's model name (`--alias`), so requests pass
-through unchanged. On Strix Halo the recipe passes Lemonade's own LLM test suite
-(`test/server_llm.py --wrapped-server onebit`) on Vulkan and HRX. It is being
-prepared as a pull request to `lemonade-sdk/lemonade`.
+through unchanged.
+
+The recipe lives in our Lemonade fork,
+[1bit-MONSTER/lemonade](https://github.com/1bit-MONSTER/lemonade): upstream
+Lemonade plus the `onebit` backend (fork PR #1). Build `lemond` from the fork and
+put `1bit` on PATH (or set `$LEMONADE_ONEBIT_BIN`):
+
+```sh
+git clone https://github.com/1bit-MONSTER/lemonade && cd lemonade
+cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release -DBUILD_WEB_APP=OFF
+cmake --build build --target lemond lemonade
+LEMONADE_ONEBIT_BIN=/path/to/1bit build/lemond
+```
+
+On Strix Halo the recipe passes Lemonade's own LLM test suite
+(`test/server_llm.py --wrapped-server onebit`) on Vulkan and HRX: 31 tests, 9 run,
+22 skipped as unsupported. It is not proposed upstream. Lemonade asks for an RFC
+before a new backend.
 
 ## On its own