The user directed repair of the DEV-to-TEST process and clarification of TheWell finding #559. TheWell PROD was not promoted. AutoCoder Engine itself follows its previously authorized automatic main delivery policy.
dev as 9ae2579c56bc7cf162caef7b61acfbe5f8e49e95. It adds a member-specific test_branch route for TheWell Backend, preserves the former direct route for other members, and displays linked blocked requirement evidence and an unassigned review owner on finding cards. Its feature-branch worker validation passed. Candidate run 3974 then failed at test compilation with two missing store arguments and one moved test value; no deployment was made from that candidate.dev as ae60f950296a77104ecbeb4059cc6b82ad5a7b85. Feature-branch worker validation passed. Full candidate run 3976 passed candidate validation, finalization, TEST deployment and previously authorized automatic main integration/production delivery.ae60f950296a77104ecbeb4059cc6b82ad5a7b85-3976-1 is recorded production_live. Release deployment records show healthy TEST at 10:21:08 UTC and healthy production at 10:21:56 UTC. Both backends and frontends expose the exact ae60f950 revision externally; main and dev have the same source tree.direct_test_pipeline_mode; the TheWell Backend member UUID 203fdc1d-37bb-48d8-8b0d-abb43f1de914 is test_branch. Its pre-migration row matched pipeline 394 and Deploy exact build to persistent test. Other members default to development_direct.The live SuperProject response still reports finding #559 open with workflow_status=waiting_for_human, no recorded owner, and linked REQ-0083 active / REQ-0094 blocked in its import snapshot. The newly deployed card projection shows the blocked REQ-0094 title, labels the review owner unassigned, and says no personal task is assigned. It cautions that the import is a snapshot; current source has REQ-0083 implemented and REQ-0094 blocked pending credential-owner rotation/revocation evidence. This change does not close the finding or invent that evidence.
A temporary credential-free browser acceptance Pod was attempted on drg-k8s-worker-01 to inspect the card through the UI. Kubernetes rejected it before start with OutOfcpu (15875m already requested of 16000m, new request 200m). The Pod was deleted, and no task directory was created. Thus the actual rendered card was not independently browser-verified; source tests, exact deployed frontend revision, and live finding data are the available evidence. Do not treat this as user acceptance.
If AutoCoder rolls back to a pre-route binary, pause TheWell delivery reconciliation before that binary can process new change sets or remove the member's direct route until the route-aware binary is restored. The host relay and Azure TEST YAML independently deny DEV-sourced TEST deployment. Preserve the successful TheWell TEST branch release and the original completed #559 change-set history.