[arthurfiorette]

Adds one check for branch rules to require, and cuts the jobs that fail on purpose from two to one.

• CI passed (gate) needs every job except the expected failure. It runs with always(), because GitHub counts a skipped required check as passed. It fails if any job it needs failed, was cancelled or was skipped, and lists which ones.
• Logs without access to the jobs API no longer has a failing step. With a token the API refuses, the post step can't tell whether a step failed, so it uploads anyway. The job can therefore pass, and the artifacts job still checks the upload and the fallback name.
• Failed test step is renamed to Expected failure: test step. It has to fail for real: with continue-on-error on the step, the jobs API reports the step as success (seen on "Failed start on ubuntu-latest"), and the action correctly uploads nothing. A run dispatched from CI wouldn't help either, since its checks attach to the same commit. The artifacts job needs this job and checks its logs, which is why the gate leaves it out.

After merging, require only CI passed in the branch rules.

#4 adds a lockfile job. Whichever of the two PRs merges second should add lockfile to the gate's needs. The unnamed change appears in both PRs and is identical, so it merges cleanly.

[mira-arthur]

Mira PR Walkthrough

Adds a CI passed gate job to the CI workflow so branch rules can require a single check. The gate runs with always() and fails if any needed job failed, was cancelled, or was skipped. It also reduces intentionally failing jobs from two to one: the "Logs without access to the jobs API" job no longer has a failing step, and the failing test step is renamed to "Expected failure: test step".

Confidence: 4/5   ◉◉◉◉○   Safe with minor follow-up

• The change is confined to one workflow file and the gate logic fits the description. A follow-up is needed to add lockfile to the gate's needs when PR Read the devlanes version from the project's lockfile when version is not set #4 lands, and to require only CI passed in the branch rules after merge.

1 file reviewed

---

Comment @mira-arthur help to get the list of available commands and usage tips.