A SHA in `ref` died with "Remote branch <sha> not found" (killed the
2026-11-06 sim publish of SHA f0e206ff3: dispatch ref=branch +
inputs.ref=<sha> is the publish-day pattern, since the Gitea dispatch
API only accepts branch names). SHA-shaped refs now init+fetch the sha
explicitly (the server allows anySHA fetch); branch/tag refs keep the
exact old path. Sparse path already fetched this way.
Co-Authored-By: Ozan Bozkurt <ozan@tinqs.com>
Co-Authored-By: ZCode <GLM-5.3 via ZCode>