ci(lint): use CI_PYTHON_LAUNCHER from runner config as single source of truth

Configure system Python path once in runner/config.yaml (runner.envs) instead of probing N candidate locations in the workflow. Workflow now fails fast with a clear error if the env is unset or points to a missing file. Document the new env in AGENTS.md.
2026-05-14 22:56:51 +02:00
parent 3c62bbbcbb
commit 4f656725bf
3 changed files with 22 additions and 44 deletions
@@ -191,6 +191,11 @@ NON modificare il branch WinRM esistente quando si lavora sul branch Linux e vic
  - `GITEA_CI_ARTIFACT_DIR` — `F:\CI\Artifacts`
  - `GITEA_CI_GUEST_CRED_TARGET` — `BuildVMGuest`
  - `GITEA_CI_SSH_KEY_PATH` — `F:\CI\keys\ci_linux`
+  - `CI_PYTHON_LAUNCHER` — absolute path al Python di sistema usato per
+    bootstrap del venv produzione (`F:\CI\python\venv`). act_runner gira come
+    SYSTEM con PATH sanitizzato (no `python`/`py.exe` risolvibili), quindi i
+    workflow Python leggono questo env come single source of truth. Aggiornare
+    solo quando si fa upgrade dell'interprete.

 ---