chore: align forge economics workplan and adopt FORGE-WP- prefix

Measure live Gitea-compatible forge. Keep historical RAILIANCE-WP-0002
id. New workplans use FORGE-WP-.

workplans/RAILIANCE-WP-0002-forge-resource-economics-evidence.md

@@ -8,9 +8,10 @@ status: ready
 owner: codex
 topic_slug: railiance
 created: "2026-08-11"
-updated: "2026-08-11"
+updated: "2026-08-15"
 related:
   - RESOURCE-WP-0003
+  - ADR-0008
 state_hub_workstream_id: "72f935a5-d921-48a4-96e4-2365556c7374"
 ---
 
@@ -23,6 +24,21 @@ evidence for `resource:railiance:forgejo`, which supplies source and package
 infrastructure to Helix Forge and the wider federation. Origin:
 `RESOURCE-WP-0003-T04` delegated evidence gap.
 
+Measure the live Gitea-compatible Helm workload
+(`deployment/forgejo-gitea` on `reef-railiance`). Forgejo is the
+migration target, not a second live product. Keep the resource id
+`resource:railiance:forgejo`.
+
+This id uses the historical `RAILIANCE-WP-` prefix (collides with other
+ownership repos). New forge workplans use `FORGE-WP-`. Do not change
+this file's `id` or hub UUID.
+
+Do not add a public metrics or economics endpoint (ADR-0008). Collect
+in-cluster or via the operator tunnel. Existing public Forgejo HTTPS is
+a separate granted surface, not this plan. Do not treat
+`environment: production` in resource-control as ADR-0006
+`production-approved`.
+
 ## T01 — Measure Forgejo demand and utilization
 
 ```task