forked from unom/punktfunk
enricobuehler
1b52942bf8
`build-rust` / `build-gamescope` were compared only against the STRING 'true'. A checkbox from the Gitea UI arrives that way, but an API dispatch can deliver a real JSON boolean, and the comparison then misses — the step is skipped, the job still reports success, and the log is indistinguishable from a run that had nothing to do. MEASURED 2026-08-19: dispatched with build-gamescope=true to verify the flake.lock bump actually fixes the gamescope patch set. Run 19320 went green with 'Build the patched gamescope' SKIPPED — a green that proved nothing about the one package being fixed, on the exact check the header recommends before merging a lock bump. Accepts both shapes now. Deliberately still no `inputs.*`: that context is what Gitea's parser is least reliable about, which is why this file used github.event.inputs in the first place.