workplans: add FORGE-WP-0009 to retire stale Gitea deploy assets

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 99543@bnt-lap001
Assistant-Session: 05d24177-20b9-4e96-a91b-b73be1d6e99e

workplans/FORGE-WP-0009-retire-stale-gitea-deploy-assets.md

@@ -0,0 +1,55 @@
+---
+id: FORGE-WP-0009
+type: workplan
+title: "Retire stale Gitea deploy target and CoulombCore Gitea values"
+domain: financials
+repo: railiance-forge
+status: proposed
+owner: codex
+topic_slug: railiance
+created: "2026-10-18"
+updated: "2026-10-18"
+flavor: implementation
+depends_on: []
+---
+
+Small cleanup found while finishing FORGE-WP-0006. Gitea is retired; the live
+Forgejo release source is `railiance-apps/helm/forgejo-values.yaml`. Two assets
+in this repo still describe the old setup and can mislead an operator. No
+production change is part of this plan; it only removes or redirects repo files.
+
+## Remove or redirect the stale gitea-deploy target
+
+```task
+id: FORGE-WP-0009-T01
+status: todo
+priority: high
+```
+
+`make gitea-deploy` runs `helm upgrade --install forgejo gitea-charts/gitea`
+with `helm/gitea-values.sops.yaml` and `helm/gitea-registry-values.yaml`, not
+the live release source. Running it could overwrite production Forgejo with
+stale settings. Compare those values read-only against the railiance-apps
+release source, then either delete the target (and the values files if unused)
+or make it delegate to the railiance-apps release entry point. Check
+`gitea-ingress-deploy` and `manifests/gitea-ingress.yaml` the same way, and
+update `docs/deploy-capable-gitea-move-review.md`,
+`docs/current-forge-asset-inventory.md`, `.claude/rules/stack-and-commands.md`
+and README. Coordinate with railiance-apps owners if their docs point here
+(`railiance-apps/docs/forgejo-on-railiance01.md`).
+
+## Delete the CoulombCore Gitea release values
+
+```task
+id: FORGE-WP-0009-T02
+status: todo
+priority: medium
+```
+
+`releases/gitea/values.yaml` is the old CoulombCore Gitea release (chart
+gitea/gitea 12.5.0, namespace default) and contains the placeholder
+`adminPassword: changeme4`. Confirm no live release still uses it, then delete
+it and update the references in `docs/current-forge-asset-inventory.md` and
+`railiance-apps/docs/forgejo-on-railiance01.md`. If that placeholder was ever a
+real password anywhere, route its rotation through OpenBao custody
+(`warden route find`), not through this repo.