docs: migrate repository guidance to Gitea

docs/benchmark/README.md

@@ -7,9 +7,9 @@ the benchmark fixtures. The latest full functional coverage run passes 652 tests
 across 34 files under the 2 GB Node heap limit, excluding the separate benchmark.
 This does not establish a passing performance protocol.
 
-MR pipeline 320 passed all 652 functional tests in 109.43 seconds, then the
-seven-scenario protocol timed out at its unchanged 300-second limit without an
-out-of-memory failure. In an earlier diagnostic run, the loaded-year warm-up took
+Before the Gitea migration, GitLab pipeline 320 passed all 652 functional tests
+in 109.43 seconds, then the seven-scenario protocol timed out at its unchanged
+300-second limit without an out-of-memory failure. In an earlier diagnostic run, the loaded-year warm-up took
 184.36 seconds and its first measured repetition began about 251.78 seconds into
 the protocol. Those diagnostic timings precede the final period-projection cache
 and the planned original-decision-trace removal, and are not a result for either.
@@ -19,12 +19,15 @@ 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, CI runs the benchmark in a separate job with
-`allow_failure: true` while #78 is open. Functional coverage tests and all other
-required checks remain blocking. #78 must restore the required benchmark gate
+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
+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.
+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
+[CI migration status](../../README.md#continuous-integration).
 
 The results below document earlier implementations and protocols. They are
 historical measurements rather than the performance result for composable rules.