monoscope/ci/checks.tsv
Anthony Alaribe 72a7b4b47e
repo-lint check: actionlint over the workflows and hpack-check over monoscope.cabal (#866)
Nothing parsed the workflows (#859 broke Deploy with an expression no check read), and CI
regenerates monoscope.cabal before building, so a stale committed file (#858) passed every gate.
2026-11-11 18:07:26 +01:00

2.2 KiB

1# `make ci` (scripts/ci/ci.sh) read this file, so a check can never exist in one
2# and not the other.
3#
4# name requires inputs
5#
6# requires space-separated capabilities the environment must provide for the
7# check to be RUNNABLE and for its result to be TRUSTED. The gate only
8# reuses an attestation whose recorded capabilities are a superset of
9# these, so a run that fell back to a stub service can never satisfy a
10# check that needs the real one.
11# inputs pathspecs whose content the check's result depends on. @-names expand
12# to the sets in scripts/ci/ci.sh (see PATHSET_*). Every check also gets
13# @meta (this file + the runner + the workflows), so changing what a
14# check DOES invalidates it everywhere.
15#
16# Narrow `inputs` only where it is provably sound. A too-wide set costs a rerun;
17# a too-narrow one ships an untested change.
18# Parallel integration, UI, and e2e lanes share dependency installs prepared by
19# the runner before launch; each check still declares its own source inputs.
20# Integration installs SDK/media tools and runs the VM-free SDK protocol tests.
21# Container VM cases remain pending without
22# guest assets and a hypervisor; provisioned hosts verify those cases separately.
23# Shards require clean summaries and successful process exits; diagnostic text
24# and test names do not determine their result.
25# CI regenerates monoscope.cabal and never parses the workflows, so nothing else checks either.