TheWell Backend dev is for agent and local worker validation. The Azure test branch is authoritative for the persistent TEST deployment. This change does not promote to production. The user directed this repair after DEV had deployed to TEST while the TEST branch remained stale.
dev as d2dd2167336f8aec792c1df99face0ee0c5cc5b7: TEST pipeline admits only refs/heads/test, verifies current TEST HEAD before and after deployment, and the normal Azure pipeline admits MAIN only. Gitea worker workflow builds DEV and TEST, publishing immutable artifacts only for TEST.93a8216b5111557f5239c94ab3002efa39dff1c7. Conflict resolution kept the newer DEV requirements catalog and MAIN-only pipeline; the resulting TEST tree equals the reviewed DEV tree. No branch reset or force push occurred.da611f8bdb36940e723367ead7278779fca45a98. /usr/local/lib/thewell-local-build-mirror/{sync,relay,package_retention}.py was updated from that reviewed source. Source mirror now copies DEV and TEST refs to private Gitea without force push. Relay accepts only an exact TEST worker receipt and TEST branch Azure run. ProfileBackups PR 17 updated the source-mirror systemd descriptions to name both branches; the corresponding unit files were installed and systemd reloaded without changing timer interval.d2dd216 and TEST 93a8216.refs/heads/test. Gitea worker run 9101 reported success for 93a8216 and produced a source-bound receipt with archive SHA-256 values. The relay attached that artifact to Azure TEST run 26196, which completed successfully at 10:02:26 UTC. Its exact TEST Deploy stage succeeded, including internal namespace readiness. The relay marked the exact TEST revision completed. Public TEST root returned HTTP 200; an unauthenticated backend readiness URL was not an exposed route (HTTP 404), so no signed-in user acceptance is claimed.Azure TEST run 26196 succeeded at 10:02:26 UTC with exact TEST branch SHA 93a8216, current-head checks before and after deployment, and internal backend readiness verification. The relay recorded completed. DEV PR 6651 closed at 09:50:39 UTC and its exact Gitea worker status succeeded at 09:51:32 UTC (52 seconds). TEST PR 6652 closed at 09:55:35 UTC; its exact worker status succeeded at 09:56:36 UTC (61 seconds), and Azure run 26196 completed at 10:02:26 UTC (6 minutes 51 seconds after TEST merge). These are observations from this real change, not a sustained performance guarantee. Signed-in user behavior was not retested in this run. Do not infer production promotion. The previous TEST release and Kubernetes rollback records remain preserved. If the new TEST run fails, keep the relay in a failed state, diagnose its exact stage, and repair TEST from the same reviewed branch route; do not restore DEV-direct delivery.