mkit CI preflight

mkit splits its CI across two systems: GitHub Actions and Google Cloud Build (GCB). A green GitHub rollup is not proof the PR is mergeable — the Linux Rust gate, docs-lint, supply-chain, codegen-freshness, and unsafe-ceiling checks all live on GCB and post their own commit statuses named mkit-*-pr. Path filters, fork gating, and stale merge-refs can each leave a required check silently absent while the PR still shows green.

This skill is a pre-merge preflight: enumerate the checks that must pass, confirm they actually ran, and clear the subsystem traps. Work the steps in order.

Ground truth first

The check names and gates below are the current design, but CI configs move. Before trusting this list, reconcile it against the repo: