Nguyen Minh Phuc b02d4e85c6 ci: record that act_runner ignores max-parallel ...

The previous commit claimed max-parallel: 1 would stop two image builds from
starving each other. It does not — act_runner ignores strategy.max-parallel.
Run #14 had it set and still ran the worker leg from 04:25:47 while reconciler
was still building, after api had run alone from 04:23:03 to 04:24:04.

That run failed a different way: actions/checkout could not reach Gitea at all
(`Failed to connect to gitea-http:3000 after 3105 ms`) while two runs were in
flight, with node0 at 140% memory. Same root cause, new mask.

The setting stays, since it is correct on runners that honour it, but the
comment no longer claims it does anything here. The binding lever is the
runner's `capacity`, dropped 2 -> 1 in oci-k8s.

2026-07-20 04:27:48 +00:00

..

ci.yaml

ci: record that act_runner ignores max-parallel

2026-07-20 04:27:48 +00:00