DR-055 — Deployed-producer bundle hosting: persistent-volume clone + repo-scoped deploy key, push as a separate lane

Retired/tombstoned S504. Discharged: id-134 archived, the {132.35} dispatch gate discharged, full E2E (clone → producer commit → push) proven as the ops surface. Retire owner-ratified S504. Substance home: reference/deployment-architecture.md §4 + canonical:scripts/cocoindex_pipeline/producer/publish.py. Original ADR text retained below; this id stays on disk so citations resolve and the number is never re-issued. ID-134-adjacent; discharges the {132.35} dispatch gate. The deployed producer (ca-pipeline-platform-staging first) resolves OKF_BUNDLE_DIR (the producer env var; the app-side viewer’s parent-dir env is OKF_BUNDLE_ROOT — distinct) to a persistent-volume clone of the bundle repo (platform: canonical-okf-showcase, renamed from canonical-okf-platform per bl-479, S487); a repo-scoped read-write deploy key, mounted as a Coolify secret, authenticates a post-run push step — a separate lane, because git_sync deliberately stays commit-local and never creates or pushes remotes (its S453 contract). Full E2E (clone → producer commit → push) is the proven ops surface, not commit-local-only. The deployed producer’s manual forced-run surface is the bearer-gated POST /producer-run endpoint (loopback-only, never Traefik-routed — reference/deployment-architecture.md §4, S491 refresh).