TheWell Backend DEV source remains authoritative in Azure DevOps. A private, non-force Gitea mirror of exact DEV revisions triggers the existing worker-host Gitea runners. A successful build publishes immutable application and Kubernetes archives plus their SHA-256 receipt. The controller relay binds that receipt to an Azure TEST pipeline run at the same full source revision, uploads and reads back both archives in that run's existing Build Artifact container, then Azure pipeline 394 deploys without compiling.
The final DEV commit 0585e7a922e10126efcdca72d5f5211d9ed0ae92 merged at 17:15:57 UTC through PR 6635. Gitea run 7 changed from pending at 17:16:17 to success at 17:17:06 (49 seconds). Azure TEST run 26175 completed successfully at 17:21:59 (6 minutes 1 second from merge). Its deploy task reported the exact source and app tree hash 40625f6d8cd15c965af9039d8ca033dc13fbed5d12a1d28efb4bcf73289bb708, a healthy backend rollout and persisted synthetic fixture. The public TEST site returned HTTP 200 afterward. The relay state is completed for that exact revision/run. Legacy hosted Azure DEV pipeline 339 has no run for this commit; its latest run remains 26173 for the prior revision.
host/thewell-local-build-mirror/. Installed services and timers: thewell-source-mirror.service/.timer and thewell-artifact-relay.service/.timer, one-minute cadence. The source mirror is bounded to 128 MiB with a 10 GiB controller free-space floor. State and append-only events live under /home/ax_julian/temp/thewell-local-delivery-20260928/, mode 0700; credential identities remain in the restricted .codex/secrets/thewell-local-delivery/identities.json, mode 0600.TheWell/TheWell-Backend; .gitea/workflows/backend-local-build.yml builds with .NET 8 on worker-host runners and publishes the complete package receipt last. The controller alone mints a short-lived Azure token from the existing AutoCoder service principal. The runner gets no Azure credential.dev from legacy Azure CI triggers. main remains the configured legacy trigger in the DEV copy; the production branch and production deployment were not changed.19bc2886ed682ae30cee3cbcdf16b2779613f4dd before the final cutover run.The relay stops on uncertain Azure queue results or a failed deployment; it does not auto-retry a failed revision. Inspect the exact run timeline and only the failed task, then preserve the original state and append a specific supersession decision after a reviewed repair commit. Do not force-push the mirror, delete recovery Secrets/releases, or replace credentials to make progress. TEST deployment retains its prior immutable recovery Secret and existing rollback path; verify the live release identity after any failure. To stop new handoffs, stop/disable the two timers while preserving their state, mirror and packages. Resume only after checking the exact Azure DEV and Gitea source revisions.
TheWell PROD promotion remains stopped. Existing PROD automation on the main branch has not been switched to consume the exact TEST artifact, and no PROD run was attempted. The tested local-build-to-TEST path is operational. An older signed schema-2 candidate already binds a frontend/add-in artifact pair. Exact-artifact PROD execution and acceptance of the current TEST backend pair remain separate work under the active production stop.
The live AutoCoder engine Deployment identifies source revision dc326e5e57528939554c158b31e8f86df712e230, candidate run 3953, deployed at 15:49 UTC. Its direct-TEST provider reconciliation code is present in that revision. The authoritative change set sp-requirements-1790540402214217888 is completed: its single outcome is test_delivered, DEV and TEST revisions are both 1232efc05bf95e888431d086c52d0b0be673287b, and its direct TEST route is Azure definition 394 stage “Deploy exact build to persistent test” with successful run 26156. The earlier DEV PR transition needed an exact operator reconciliation at 10:14 UTC; no operator TEST-delivery SQL record was found. This distinguishes that manual recovery from subsequent engine TEST reconciliation.
Read-only Azure source fetch showed PROD main at 636a974fa958bbafd6cfcd3f0516b9ecb955fa62, with a 94-file DEV difference. Its azure-pipelines.yml still triggers a hosted build and deployment for main; no PROD change was made. The DEV azure-pipelines-promotion-admission.yml is diagnostic only. The acceptance producer and finite-retention owner were separately activated through the existing administrator route; the production execution stage and safe immutable release migration remain absent. These are concrete reasons why the successful backend TEST delivery is not an authorized exact-artifact PROD promotion. Keep the production stop and do not infer promotion approval from a pipeline parameter, branch movement or successful TEST run.
Live host state supersedes the source document's historical activation language. The restricted Ed25519 signing key and owner journal exist; thewell-test-retention.timer is active. An on-demand run of its existing service completed successfully at 17:30:25 UTC with one eligible pair, two retained runs, 115,504,150 retained artifact bytes and no expiry attention. The signed Wiki index sequence 5 was verified under the reviewed public key, is valid until 17:40:24 UTC, and binds candidate b26124-f26129-20260927T133407Z. Its signed acceptance record binds backend run 26124 and frontend run 26129. Azure retention leases 22643 and 22644 were read back and verified with the candidate owner and remaining validity. The index is intentionally refreshed on demand for admission and is not permanently fresh.
This accepted pair is older than the current TEST backend run 26175; the earlier human observation cannot be silently transferred to the newer backend artifact. The trusted admission verifier remains read-only and reports productionAuthorized:false. Azure PROD pipeline 339 last completed main revision 636a974fa958bbafd6cfcd3f0516b9ecb955fa62 in run 25940 on 2026-09-24; it still builds on a hosted agent and deploys through the legacy overwrite path. An old main run 25271 remains provider-inProgress with Build succeeded and Deploy pending since 2026-09-05; no mutation of that run was made. The active PROD stop and missing immutable production migration continue to block promotion.
The owner clarified that this delivery issue is resolved when the fix works in TEST. PROD promotion is outside this issue and will resume with a later periodic update. The active PROD stop remains in force; this record's PROD migration notes are a separate follow-up, not a completion gate for the DEV→TEST repair. Current read-back: local Gitea build status success for DEV 0585e7a922e10126efcdca72d5f5211d9ed0ae92, Azure TEST run 26175 completed with the exact deployment stage succeeded, public TEST returned HTTP 200, and the AutoCoder REQ-0083 change set remains completed/test_delivered at DEV/TEST revision 1232efc05bf95e888431d086c52d0b0be673287b with Azure TEST run 26156 succeeded.
Azure TEST run 26182 failed before switch because the 14-entry immutable backend release directory cap was full. The artifact relay is fail closed and now refuses newer ordinary releases. The latest REQ-0070 TEST cutover used a reviewed configuration-only path (Azure PRs 6642 and 6643, run 26184 succeeded) against already verified application source 721fb5170dbe150ec0d5052b39ae339d42848464; it allocated no new release directory. The 14-entry immutable recovery Secret cap is separate and may block the next full release as well. Do not describe the normal DEV-to-TEST artifact relay as operational until retention is reconciled and an exact subsequent full delivery succeeds. No release or Secret was deleted, cap raised, or PROD route changed. The precise inventory, preservation and recovery implications of any retention cleanup must be reviewed under the host storage and destructive-operation rules before removing old durable state.
The owner approved a bounded ongoing cleanup for unreferenced TEST releases, recovery Secrets, and obsolete private Gitea build packages. Azure DEV PR 6644 added a read-only release/rollback inventory; run 26185 succeeded and identified the exact capacity fault: 14 release directories, 13 recovery Secrets, 626,688 KiB available on the 2 GiB release PVC, with four directories and three Secrets unreferenced by live Deployment or retained ReplicaSets. Azure DEV PR 6645 merged the fail-closed pre-stage cleanup at revision c763322aa7bf61e6709f6d3b1ecb888e09f97612. Canonical host ProfileBackups PR 14 installed package retention ahead of mirror sync. It protects recent builds, the current relay revision and the two latest successful TEST revisions; its first live run removed only obsolete package versions c914cb5c... and 28cf2644..., leaving nine packages under the 12-entry worker cap.
Normal exact-artifact Azure TEST run 26186 succeeded for source c763322aa7bf61e6709f6d3b1ecb888e09f97612. Its retention receipt records deletion of only unreferenced release directories from runs 26062, 26077, 26083 and 26172 and matching recovery Secrets from 26062, 26077 and 26083. The receipt shows ten directories and ten recovery Secrets before the new release was staged, with 942,080 KiB available and the 512 MiB reserve satisfied. Its deployment receipt records healthy rollout of release c763322aa7bf61e6709f6d3b1ecb888e09f97612-26186, rollback not needed, and the existing isolated TEST database/Entra configuration active. The relay recorded this exact run completed.
Read-only follow-up Azure run 26187 succeeded. Its live inventory shows generation 752 observed, one ready backend replica, source/release c763322aa7bf61e6709f6d3b1ecb888e09f97612-26186, 11 release directories, 11 immutable recovery Secrets, and 942,080 KiB available on the 2 GiB PVC. The accepted run 26124 remains retained. The recurring cleanup protects every release referenced by the live Deployment, owned ReplicaSets, or backend Pods; it fails closed if ownership, readiness, permission, reserve, or capacity checks cannot be proved. The normal DEV-to-TEST artifact route is restored at this exact release. This is one real successful recovery delivery, not a claim of measured performance across future changes. TheWell PROD was not changed; authenticated application behavior for the newer artifact remains a separate acceptance check.