The fork only needs its own deploy pipeline (.gitea/workflows/deploy-custom.yml).
All 17 upstream workflows (bot-help, pr-review, oc-review, mobile-ci, release,
stale, vscode-extension, etc.) are noise on this fork — they target upstream's
bot accounts, macOS/mobile release machinery, and comment triggers that don't
apply here. They were also failing with 'Resolve pull request context' errors
because they're designed for upstream's environment, not our fork.
bot-hermes
99edcbb24c