Close verified incident task and finish local workplan loose ends

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e3c3-621b-7350-9f77-50a8d3ee7657

workplans/RPF-WP-0043-policy-nexus-argocd-onboarding.md

@@ -4,12 +4,12 @@ type: workplan
 title: "Onboard rapp-policy-nexus to the ArgoCD production lane"
 domain: financials
 repo: railiance-platform
-status: active
+status: blocked
 flavor: planning
 owner: railiance-platform
 topic_slug: railiance
 created: "2026-09-21"
-updated: "2026-09-22"
+updated: "2026-09-27"
 due: "2026-12-21"
 related: [RPF-WP-0022]
 state_hub_workstream_id: "ec41a4bd-df18-5b07-9b63-ccb80d9f001c"
@@ -231,3 +231,7 @@ the inventory.
 - **T05 done.** Gap declared and inventoried in
   `docs/direct-apply-gap-inventory.md`, with a per-group proposal for the
   founder. No target changed.
+
+## Loose-end review — 2026-09-27
+
+The workplan is blocked on the source-owner agreement and its downstream adoption gates. RAPP-POLICY-NEXUS-WP-0002 proposes a multi-source Application: chart in rapp-policy-nexus and release values in railiance-apps. This supersedes the earlier platform-only suggestion to put production values in the package repository. The platform accepts that shape and the helm/policy-nexus path exception in principle; it still needs railiance-apps acceptance, an actual committed values path/revision, source access and a zero-diff render before T02/T03 can close. No owner acceptance or cross-repository change is inferred. T01 remains proven by current railiance01 Synced/Healthy evidence.