scriberr: no upstream contribution (Prime) — drop prepared PR text; patches carried locally

stacks/scriberr/patches/README.md

@@ -7,7 +7,7 @@ distinctly tagged image, and proves it before anyone deploys it.
 
 | patch | against | status |
 |---|---|---|
-| `0001-parakeet-pause-aware-slicer.patch` | upstream `a353078` (HEAD 2026-09-20) | **LIVE on fv-ml1 since 2026-09-30 1211 PT** as `scriberr:local-blackwell-a353078-slicer1`; upstream PR **prepared, not opened** (`upstream-pr/`) |
+| `0001-parakeet-pause-aware-slicer.patch` | upstream `a353078` (HEAD 2026-09-20) | **LIVE on fv-ml1 since 2026-09-30 1211 PT** as `scriberr:local-blackwell-a353078-slicer1`; superseded in production by 0002 on top of it; **no upstream PR (Prime, 2026-10-01)**. Both patches are carried locally only |
 | `0002-parakeet-model-path-and-gap-retry.patch` | 0001 | **LIVE on fv-ml1 since 2026-09-30 1602 PT** as `scriberr:local-blackwell-a353078-dropout2` (Prime: "Scriberr gets the basic fix, no surgery for the new toolkit"; v3 stays). Live check: a 20-min file peaked at 5,502 MiB on GPU 3, `retried_gaps: 1`, +29 words against the slicer1 image. Why: `docs/pfi/parakeet-dropout-investigation-2026-09-30.md` |
 
 
@@ -15,8 +15,7 @@ Rollback for the live deploy: `SCRIBERR_IMAGE=scriberr:local-blackwell` (the
 unpatched image, kept), or restore `/opt/docker/compose/scriberr/.env.bak-20260930-pre-slicer1`,
 then `sudo -n docker compose up -d scriberr`.
 
-Ruling: Prime, 2026-09-30, "build the slicer". Opening the upstream PR is
-outward-facing and needs Prime's explicit yes.
+Ruling: Prime, 2026-09-30, "build the slicer". **No upstream contribution (Prime, 2026-10-01: "no upstream for scriberr").** The prepared PR text was removed (it remains in git history, ee3db68).
 
 ## 0001 — pause-aware Parakeet slicer