#2 Run make verify on every pull request and in the merge queue

What this is

The repo's one required check: workflow factory, job verify. It runs make verify, then python3 -m tools.mutants, on the commit and nothing else.

Property	How
Runs on every pull request and in the merge queue	pull_request and merge_group, no path filter, so a required check on it always reports
Runner pinned by version	ubuntu-24.04
Action pinned by commit	actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1, which the GitHub API returns as the commit of release v7.0.1. Looked up, not guessed
Least privilege	Workflow permissions: {}; the job holds contents: read; persist-credentials: false
Bounded	timeout-minutes: 15
Nothing installed	The runner's own python3; the repo uses the standard library only

The file is, word for word, examples/workflows/verify.yml from the local branch slice-0/context-engineering, so that branch's workflow standard and its example agree with the real file when it lands.

Verification

This pull request is the workflow's first run: the check on it is the evidence. Locally, make verify and python3 -m tools.mutants pass on this branch (19 of 19 mutants killed).

What follows, and is not in this change

• The ruleset on main (this check required, the merge queue, no direct pushes, no required approving review yet) is applied after this merges, once the check name GitHub reports has been read from this run.
• Known for the branch slice-0/context-engineering: once .github/workflows/ exists, its tools/check_context.py asks three decision records (0001 boundary 5, 0005 boundary 4, 0008 boundary 7) to name the check that holds them. That is the check working as written; the records are updated on that branch.

🤖 Generated with Claude Code