bvandeusenandClaude Opus 5 2c88ad3efb ci: report the raw and normalised trigger values ...

The refresh dispatch on run 5265 went green with every step skipped: the
main-only guard did not fire, checkout took dev, and the reuse step read
IS_REFRESH as false. So both workflow-level expressions evaluated false while
the identical accessor works for force_build, which compares its value in the
shell rather than in an expression.

That is a guess until it is measured, and the failure is silent by
construction — a refresh that evaluates false behaves exactly like an ordinary
push and reports success. This prints the raw input beside the normalised
value in the step that already exists to say what a run derived, so the two
disagreeing is visible rather than inferred.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TTjbZZ6JirCMSaJzQV1RhA

2026-09-02 14:58:20 -04:00

..

baseline.yml

docs+ci: folder import stays retired, and fix a readiness probe that never probed

2026-09-02 00:51:25 -04:00

build.yml

ci: report the raw and normalised trigger values

2026-09-02 14:58:20 -04:00

ci.yml

docs+ci: folder import stays retired, and fix a readiness probe that never probed

2026-09-02 00:51:25 -04:00

extension.yml

ci(extension): retire the manual-bump guard, true up the docs (step 5)

2026-08-27 11:29:44 -04:00

release.yml

ci: a release publishes a changelog, not an image (318 step 7)

2026-08-28 20:57:25 -04:00