Record RPF-WP-0044-T05: target-revenue adopted (proving period).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703

workplans/RPF-WP-0044-argocd-phase-b-adopt-existing-applications.md

@@ -256,12 +256,14 @@ whitelist. Live check: `rapp-issue-core make verify-live`. Workload restore:
 
 ```task
 id: RPF-WP-0044-T05
-status: wait
+status: progress
 priority: medium
 state_hub_task_id: "d418068a-6fb0-5416-aac5-d23c93924d9c"
 ```
 
-**Waits on the founder's go-ahead.** Preconditions: T01 item 2 (CNPG
+**Adopted 2026-09-21** (founder go-ahead; custodian session). The *server-side* diff at `f1109d5` conflicted on `resources.limits.cpu` (live `1` owned by `kubectl-client-side-apply` vs declared `1000m`: the same quantity); the *client-side* diff, which is what the apply strategy uses, was rc=0 for all five non-hook objects. Child merged in `6eeb826`; manual sync with the `apply` strategy, prune off: Succeeded, Synced/Healthy, **0 Jobs created**, same pod (36d, no restart), CNPG healthy 1/1, ExternalSecret SecretSynced, `https://revenue.coulomb.social/healthz` 200 (the live check path is `/healthz`, not `/health`). Status `progress` = proving period. Automated sync still needs target-revenue's confirmation on the two hook Jobs (asked 2026-09-21). Evidence: `docs/evidence/2026-09-21-target-revenue-argocd-adoption.json`.
+
+Original preconditions: T01 item 2 (CNPG
 `Cluster` whitelisted) applied to the AppProject by hand, and `target-revenue`
 confirms the two Sync-hook Jobs (`target-revenue-migrate`,
 `target-revenue-bootstrap-binky`) are safe to re-run against production. They