BodyLog issue BodyLog/Bodylog.dev#90 was blocked in android_internal_testing because actions/upload-artifact failed against the Gitea artifact endpoint with SELF_SIGNED_CERT_IN_CHAIN.
The BodyLog repository does not own the Gitea Actions runner or artifact service deployment, so the clean fix had to be applied in the gitea Kubernetes namespace on drg-k8s.
/home/ax_julian/AutoCoder-Engine/documentation/configs/autocoder-engine/gitea-migration/gitea-act-runner-k8s.yaml.ConfigMap/gitea-act-runner-config for both runners.deployment/gitea-act-runner-2 to the managed manifest so both runners are represented.postStart build step that rebuilds local gitea/runner-images:{ubuntu-latest,ubuntu-24.04,ubuntu-22.04} tags with the internal kryptovisor-local-ca.crt installed into the OS trust store.act_runner daemon startup until the local runner images have been rebuilt with the CA.deployment/gitea-act-runner and deployment/gitea-act-runner-2 in namespace gitea.node --use-openssl-ca can reach https://gitea.app.lan/api/v1/version with HTTP 200.1467 on branch autocoder/issue-90-fitness-device-connector-xiaomi reached:
The remaining BodyLog workflow failure is no longer Gitea artifact TLS. The Play upload step fails with Google API authorization: The caller does not have permission.
Required next action: fix the Google Play Console/API permissions for the service account referenced by BodyLog's PLAY_SERVICE_ACCOUNT_JSON secret, then rerun android_internal_testing on autocoder/issue-90-fitness-device-connector-xiaomi.
act_runner 0.2.13 did not propagate runner-level or job-level Node TLS environment reliably to JavaScript action execution under this DinD setup. The tested operational path is OS CA trust in runner images plus workflow-side Node --use-openssl-ca before artifact actions.