diff --git a/workplans/FORGE-WP-0011-forgejo-resource-requests.md b/workplans/FORGE-WP-0011-forgejo-resource-requests.md
index 8c9cf05..10d3670 100644
--- a/workplans/FORGE-WP-0011-forgejo-resource-requests.md
+++ b/workplans/FORGE-WP-0011-forgejo-resource-requests.md
@@ -249,3 +249,7 @@ The founder ran the final step of `make forgejo-deploy` in their own terminal: `
 - Node requests: 3840m (96%) CPU, 78% memory.
 
 Rollback reference, if ever needed: `kubectl rollout undo deployment/forgejo-gitea -n forgejo --to-revision=14` (never `helm rollback forgejo 9`). The founder's own NetKingdom sign-in check is optional confirmation. Re-measurement after 24h/7d follows in the weekly allocation report.
+
+## Naming follow-up resolved by RAPPS-WP-0019 — 2026-10-21
+
+The forge objects are now named `forge`, `forge-http` and `forge-ssh`, with pod label `forge` (railiance-apps RAPPS-WP-0019, Helm revision 11). Still left in T04: a runner container memory limit and the stale Error runner pod from 66 days ago. The data volume and the container names keep their chart-imposed legacy names.