diff --git a/workplans/ISSUE-WP-0008-wave2-resource-right-sizing.md b/workplans/ISSUE-WP-0008-wave2-resource-right-sizing.md
index 966377e..bd31684 100644
--- a/workplans/ISSUE-WP-0008-wave2-resource-right-sizing.md
+++ b/workplans/ISSUE-WP-0008-wave2-resource-right-sizing.md
@@ -43,6 +43,8 @@ Source and container detail:
 
 - `issue-core/issue-core`: Deployment `issue-core`, container `issue-core`, `rapp-issue-core/manifests/30-runtime.yaml` (50m/128Mi) — the deploy source lives in rapp-issue-core.
 
+**Prepared 2026-10-21 (wave-2 worker W1a; not applied).** Live owner is ArgoCD Application `issue-core` (manual sync, rapp-issue-core `manifests`). Change: rapp-issue-core `11af3cb`, `manifests/30-runtime.yaml` requests 50m/128Mi → 5m/48Mi, limits unchanged. Pin: railiance-platform `30c48cb` moves `argocd/railiance01/applications/issue-core.application.yaml` targetRevision 805e124 → 11af3cb. Neither change is pushed or synced. The full manifest set against live shows only `resources.requests` on the Deployment. Apply: push rapp-issue-core, push railiance-platform (the root app updates the Application), then run a manual sync of `issue-core`. RollingUpdate.
+
 Evidence: resource-control `docs/evidence/2026-10-21-node-allocation-review/2026-10-21-node-budget.md` (+ `.json`, commit `3d9b1bd`). Rule: CPU = max(floor, p95x1.5, peakx0.5) rounded up to 5m; memory request = 7d p95 working set x1.15 (only when the change is at least 64Mi).
 
 Steps: