kevinveenbirkenbachandClaude Opus 5
afe20c0c76
The REST API answers inputs: null for a finished workflow_dispatch, so the run name is the only record of what a manual run was dispatched with. It carried one value, distros; everything else silently fell back to the workflow defaults, and a failure that only reproduces on swarm with btrfs came back green from a run that deployed all three modes on whatever filesystem it drew. Render every input as its own <emoji><value> segment instead, omitted when it holds its default, so the title carries exactly what deviates and an absent input means 'leave it on the default'. run_name derives those segments from the workflow rather than knowing them, so the format cannot drift away from the parser without a failing test. distros no longer defaults to debian -- empty draws one at random, the way untagged pushes already do. That leaves nothing in the title, so the effective list is recovered from the discover job names, matched by content against the meta/distros.yml SPOT rather than by job-name shape. Priority roles that fell behind the budget cut in every mode hold no job at all, so failed_roles cannot see them: they are neither green nor red, they never ran. Carry them along or they never deploy. --run now resolves before the selection, so it reproduces a run whatever picks the roles, not only with --failed. tests/utils/ci_*.py move into tests/utils/ci/ -- two files sharing a delimiter-bounded prefix are a folder in disguise, and the structure lint says so. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Workflow Input Resolution 🔎
Shell helpers that derive structured inputs and outputs for GitHub Actions jobs from repository state.
Scope 📋
This directory contains pure resolvers that read repository state (git history, role metadata, version tags, input environment variables) and emit resolved values either via $GITHUB_OUTPUT or stdout. Resolvers MUST be idempotent and MUST NOT mutate repository or registry state beyond writing to $GITHUB_OUTPUT. The covered concerns are distro selection for push CI, diff-driven app whitelist resolution, the 🧩 Subset label dispatch (pr_affected_roles.sh, which picks between the PR-body subset and the diff resolver), release-tag parsing, app discovery for the deploy matrix, and change detection that gates the update pipeline.
For the workflow catalog that consumes these outputs see workflows.md. For the diff-driven whitelist contract see the "Diff-driven app selection" section in pipeline.md.