ci: migrate to Gitea Actions

docs/benchmark/README.md

@@ -19,14 +19,14 @@ verification. #78 owns benchmark verification and implementation of further
 optimizations when needed, after #76 removes tracing and #77 verifies the retained
 behavior. All seven scenarios, one warm-up and two measured repetitions per
 scenario, the 2 GB heap limit and the 300-second timeout remain required for #78.
-At the user's request, the preserved CI configuration defines the benchmark in a
-separate job with `allow_failure: true` while #78 is open. Functional coverage
+At the user's request, the Gitea CI configuration defines the benchmark in a
+separate job with `continue-on-error: true` while #78 is open. Functional coverage
 tests and all other required checks remain blocking. #78 must restore the required benchmark gate
 after the unchanged protocol passes. A green pipeline during this exception
 does not establish a passing benchmark. No automatic elapsed-time planning
-cutoff is introduced. CI execution is frozen and Gitea Actions is disabled pending
-[issue #268](https://gitea.nessar.fr/nessar/vac-optimizer/issues/268); the separate
-advisory benchmark job must be carried into the converted workflow. See the
+cutoff is introduced. Gitea Actions is enabled; live workflow validation is tracked in
+[issue #268](https://gitea.nessar.fr/nessar/vac-optimizer/issues/268). The converted
+workflow preserves the separate advisory benchmark job. See the
 [CI migration status](../../README.md#continuous-integration).
 
 The results below document earlier implementations and protocols. They are