diff --git a/workplans/RPF-WP-0043-policy-nexus-argocd-onboarding.md b/workplans/RPF-WP-0043-policy-nexus-argocd-onboarding.md
index 66a95cc..ff0e2f2 100644
--- a/workplans/RPF-WP-0043-policy-nexus-argocd-onboarding.md
+++ b/workplans/RPF-WP-0043-policy-nexus-argocd-onboarding.md
@@ -71,10 +71,7 @@ ArgoCD install belongs to the cluster layer and needs its own go-ahead.
 
 ```task
 id: RPF-WP-0043-T02
-status: wait
-depends_on: [RAPP-POLICY-NEXUS-WP-0002]
-blocked_on: message-from:rapp-policy-nexus
-blocking_reason: "rapp-policy-nexus owns the tenant repository and decides manifest placement itself (RAPP-POLICY-NEXUS-WP-0002)."
+status: todo
 priority: high
 state_hub_task_id: "49143c5e-a455-526e-a26f-403dc2fb075a"
 ```
@@ -108,6 +105,17 @@ Platform checks:
 **Unblock:** rapp-policy-nexus replies with the path, the values file, and
 whether the repository is public.
 
+
+2026-10-03 (CUST-WP-0075 owner-return sweep): this task and
+RAPP-POLICY-NEXUS-WP-0002-T02 were waiting on each other. rapp-policy-nexus
+has now answered railiance-platform's 2026-09-21 question (reply `41678d1f`):
+chart `helm/policy-nexus` pinned to a tag or commit, no `k8s/railiance/` copy;
+values owned by railiance-apps, so a multi-source Application named
+`policy-nexus`; the repository is private, so ArgoCD needs a repository
+credential through its own CCR; `make deploy`/`make rollback` stop being
+production paths after adoption. The whole-workplan `depends_on` was removed
+because it made the wait circular. Next act is railiance-platform's: confirm
+the shape back to rapp-policy-nexus and draft the Application.
 ## Prepare the Application and the dry-run evidence
 
 ```task