Probe: does this Gitea honour concurrency + cancel-in-progress?

bit's versionCode design on weblib-viewer#15 would rest on a later commit
cancelling an earlier build for the same minute. That is a concurrency
group with cancel-in-progress, which is standard -- but this instance has
already contradicted four reasonable assumptions about Gitea Actions, so
it is measured rather than assumed.

Job logs are unreadable here (they 500), so the answer is carried by the
run states in /actions/tasks: two successes means the group was ignored, a
cancelled first run means it works, and a queued second run means it is
honoured but serialises instead of cancelling.

Refs weblib/weblib-viewer#15.

Co-authored-by: bit <bit@das-labor.org>

marker.txt

@@ -0,0 +1 @@
+run 1