chore(#3833): gate every PR compute lane behind a mergeability preflight (#3843)

* test(#3833): failing-first suite for the PR mergeability preflight

* chore(#3833): gate every PR compute lane behind a mergeability preflight

* fix(#3833): assert the preflight gate on parsed yaml and guard status-function if

* fix(#3833): run stub-backed cli tests in-process to avoid a spawnsync deadlock

* fix(#3833): fail the preflight open when its script is absent at the base sha

---------

Co-authored-by: sim <sim@local>
This commit is contained in:
Tom Boucher
2026-08-24 21:13:55 -04:00
committed by GitHub
parent 63abcface9
commit 6905726d9c
15 changed files with 1655 additions and 26 deletions

View File

@@ -1252,6 +1252,23 @@ does not recognize `git stash`, `git rm --cached`, `git restore --staged`, or
`git update-index --add`, any of which can also move `.planning/` content into a state a later
commit picks up.
### A conflicted PR runs no CI
Every `pull_request` compute lane waits on one shared gate, `PR mergeability`.
If GitHub reports your PR as having a merge conflict, **nothing runs** — no test
matrix, no install smoke, no mutation shards, no docs or changeset lint — until
you resolve it. The check annotates the base branch and the fix:
```bash
git fetch origin && git rebase origin/next && git push --force-with-lease
```
The gate fails **open**: if GitHub cannot tell us whether the PR is mergeable,
the pipeline runs exactly as it did before, and the per-job
`scripts/ci-rebase-check.cjs` still catches the conflict. Full reference,
including which lanes are deliberately *not* gated, is in
[docs/TESTING-SUITES.md → The mergeability preflight](docs/TESTING-SUITES.md#the-mergeability-preflight).
### CI Test Quality Checks
The following checks run on every PR in addition to the test suite: