chore(release): point overlay-htp at chore/signed-htp-lfs-store

Signed HTP bundles live on a long-lived branch of qcom-ai-hub/geniex
rather than on main, so overlay-htp and the promotion procedure both
target that branch.

Signed-off-by: Mengsheng Wu <mengshen@qti.qualcomm.com>

Author: mengshengwu

.github/workflows/release.yml

@@ -125,7 +125,7 @@ jobs:
         uses: actions/checkout@v7
         with:
           repository: qcom-ai-hub/geniex
-          ref: main
+          ref: chore/signed-htp-lfs-store
           lfs: false
           path: signed-htp-src
           sparse-checkout: sdk/signed-htp

notes/release.md

@@ -165,14 +165,14 @@ The per-tag manifest is byte-stable across workflow re-runs of the same tag —
 
 ## Hexagon HTP signing
 
-The Windows ARM64 SDK ships `libggml-htp.cat` plus `libggml-htp-v{68,69,73,75,79,81}.so` — Windows refuses to load them unsigned. Release CI runs an `overlay-htp` job **before** `build-cli` that sparse-checks-out `sdk/signed-htp/libggml-htp-<sha>.zip` from `qcom-ai-hub/geniex` (LFS-tracked), where `<sha>` is the `third-party/llama.cpp` short SHA. Both the installer and the SDK zip end up with the same HTP files:
+The Windows ARM64 SDK ships `libggml-htp.cat` plus `libggml-htp-v{68,69,73,75,79,81}.so` — Windows refuses to load them unsigned. Release CI runs an `overlay-htp` job **before** `build-cli` that sparse-checks-out `sdk/signed-htp/libggml-htp-<sha>.zip` from the `chore/signed-htp-lfs-store` branch of `qcom-ai-hub/geniex` (LFS-tracked), where `<sha>` is the `third-party/llama.cpp` short SHA. Both the installer and the SDK zip end up with the same HTP files:
 
 - **Hit** — overlay the Microsoft-signed files into the SDK artifact; `build-cli` packages them into the installer; release normally.
 - **Miss** — keep the self-signed build. The SDK name gets a `-selfsigned` suffix, and the release also carries `ggml-htp-v1.cer` (users import it) and `libggml-htp-to-sign-<sha>.zip` (operators submit it for signing).
 
 The signed bundle must contain exactly these eight files at the zip root: `libggml-htp.cat`, `libggml-htp.inf`, and `libggml-htp-v{68,69,73,75,79,81}.so`.
 
-The cross-repo checkout reuses `secrets.GH_PAT` (already scoped for cross-repo access to `qcom-ai-hub/geniex` — see `publish-s3` below). If CI reports `signed=false` but the bundle is merged on `main`, first check that `GH_PAT` has not expired.
+The cross-repo checkout reuses `secrets.GH_PAT` (already scoped for cross-repo access to `qcom-ai-hub/geniex` — see `publish-s3` below). If CI reports `signed=false` but the bundle is on `chore/signed-htp-lfs-store`, first check that `GH_PAT` has not expired.
 
 ### Promoting self-signed → Microsoft-signed
 
@@ -182,7 +182,7 @@ The cross-repo checkout reuses `secrets.GH_PAT` (already scoped for cross-repo a
    b. Submit Jenkins pipeline, fill path with `\path\to\ATT`, other field use default or first param.
    c. Get signed files from `ATT\Glymur\01000\ExtractedDrivers`.
    d. Repack the signed files (without `.inf`) into a zip with the same layout at the root.
-3. Commit the result to `qcom-ai-hub/geniex` at `sdk/signed-htp/libggml-htp-<sha>.zip` — `git lfs install` locally, add the zip on a branch, open a PR titled per [CONTRIBUTING.md](../CONTRIBUTING.md) (for example `chore(release): add signed HTP bundle for llama.cpp <sha>`), and get a maintainer to squash-merge into `main`.
+3. Commit the result to `qcom-ai-hub/geniex` at `sdk/signed-htp/libggml-htp-<sha>.zip` on the `chore/signed-htp-lfs-store` branch — `git lfs install` locally, push the zip directly, or open a PR against that branch and squash-merge.
 4. Re-run the Release workflow for the same tag.
 
 ## Windows installer signing gate