After commit 99a9f91748 changed only config.toml, the AutoCoder-Engine pipeline still ran build_backend_image for about 8m36s. The workflow classifier treated unknown root files as backend Rust changes, and config.toml was baked into the backend image. Skipping the image build without changing deployment mechanics would have failed to deploy config changes.
d25b8a5 (Deploy root config without image rebuild).config.toml is now deployed as Kubernetes ConfigMap autocoder-root-config./workspace/AutoCoder-Engine/config.toml using subPath.autocoder-root-config, patches deployment annotation autocoder.dev/root-config-sha, and waits for rollout.config.toml as runtime config/manifest work, not backend Rust work..gitea/workflows/autodeploy.yaml as CI pipeline work, not backend/frontend runtime work.autocoder-engine-ci service account was granted minimal ConfigMap permissions for autocoder-root-config.k8s/07-ci-deployer-rbac.yaml.autocoder-root-config from repository config.toml./home/ax_julian/temp/autocoder-configmap-deploy-20260509/apply.log.autocoder-engine-8747d994d-bm6jc was 1/1 Running./workspace/AutoCoder-Engine/config.toml SHA-256 matched repository config.toml: fdfbdb662bbdf809f5a6d90e9ab544fe15c468891e47cfc8bfad43791c3ce978.configmap/autocoder-root-config.563 for commit d25b8a5 completed classify in 7s and deploy_manifests in 19s.build_backend_image, rollout_backend, deploy_cronjobs, deploy_frontend, and sync_docs were skipped as intended.Future config.toml-only changes should deploy through a short manifest/config rollout instead of rebuilding the Rust backend image. Backend image builds are still required for actual Rust, Dockerfile, dependency, or runtime image changes.