bacluc-agent / agent-runner

37%

main: 37%

push

github

fix(workflows): gate the e2e image build on the composer lock

The e2e build job runs `composer install` inside the frankenphp_prod
stage of api/Dockerfile, from the committed api/composer.lock. When
the lock did not satisfy api/composer.json, that mismatch surfaced as
a bare "exit code: 4" from a long, cache-dependent image build with
no indication that a lock file was the cause, and the job never
reached the Playwright suite. The e2e result was untested, not
failed, and a full CI cycle was spent finding that out.

Validate the lock against the manifest before the build, with the same
pinned PHP 8.5.9 and Composer 2.10.3 and the same command the
`Validate Api Platform composer.lock` job in
continuous-integration-optional.yml already runs. A stale lock is now
reported at step 4 as a lock/manifest mismatch naming the offending
package, instead of as an opaque image-build failure.

The flags are load-bearing. The manifest is a private application
package with no name or description and uses exact pins, so a bare
`composer validate --strict` exits 2 on the healthy repository on
publish errors and on 60+ exact-version warnings.
`-n --no-check-all --no-check-publish` keeps only the lock-in-sync
check, and `--strict` keeps its exit code non-zero.

The gate stays fatal: no continue-on-error, no if: always(), no
`|| true`. The `Build docker image (API/PHP)` step, the job and
timeout-minutes: 20 are unchanged. This makes the failure faster and
actionable; it does not weaken it.

Refs bacluc-agent/agent-todo#348

924 of 4885 branches covered (18.92%)

Branch coverage included in aggregate %.

5299 of 11877 relevant lines covered (44.62%)

60.29 hits per line