RAPPS-WP-0019 finished; forge runner memory limit

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c

WORK-RECORDS.md

@@ -16,7 +16,7 @@
 | workplan | RAPPS-WP-0016 | active | — | workplans/RAPPS-WP-0016-forgejo-netkingdom-login.md |
 | workplan | RAPPS-WP-0017 | finished | — | workplans/RAPPS-WP-0017-reuse-private-reader-release.md |
 | workplan | RAPPS-WP-0018 | active | — | workplans/RAPPS-WP-0018-wave2-resource-right-sizing.md |
-| workplan | RAPPS-WP-0019 | active | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
+| workplan | RAPPS-WP-0019 | finished | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
 | task | RAPPS-WP-0001-T01 | done | — | workplans/RAPPS-WP-0001-cnpg-backup-scheduledbackup-coverage.md |
 | task | RAPPS-WP-0001-T02 | done | — | workplans/RAPPS-WP-0001-cnpg-backup-scheduledbackup-coverage.md |
 | task | RAPPS-WP-0001-T03 | done | — | workplans/RAPPS-WP-0001-cnpg-backup-scheduledbackup-coverage.md |
@@ -57,5 +57,5 @@
 | task | RAPPS-WP-0019-T01 | done | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
 | task | RAPPS-WP-0019-T02 | done | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
 | task | RAPPS-WP-0019-T03 | done | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
-| task | RAPPS-WP-0019-T04 | todo | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
-| task | RAPPS-WP-0019-T05 | todo | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
+| task | RAPPS-WP-0019-T04 | done | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |
+| task | RAPPS-WP-0019-T05 | done | — | workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md |

docs/forgejo-on-railiance01.md

@@ -23,7 +23,7 @@ Hostname decision: `the-custodian/docs/forgejo-production-decisions.md`.
 | Server | railiance01 `92.205.62.239` |
 | Namespace | `forgejo` |
 | Helm release | `forgejo` |
-| HTTP service | `forgejo-gitea-http` (chart naming; ingress must target this) |
+| HTTP service | `forge-http` (chart naming; ingress must target this) |
 | Chart | `gitea-charts/gitea` **12.5.0** (Forgejo-compatible; 12.6+ needs Gitea 1.26 `config edit-ini`) |
 | Image | `code.forgejo.org/forgejo/forgejo:11.0.3` |
 | Database | `forgejo-db-rw.databases.svc.cluster.local:5432` |
@@ -71,7 +71,7 @@ make forgejo-runner-status
 - `strategy.type: Recreate` in `helm/forgejo-values.yaml` — avoids leveldb queue lock
   on the shared RWO PVC during rolling updates.
 - Actions enabled via `gitea.config.actions.ENABLED: true`.
-- Ingress backend service name is `forgejo-gitea-http` (Helm release naming).
+- Ingress backend service name is `forge-http` (Helm release naming).
 
 ## Day-2 operator targets
 

manifests/forgejo-runner.yaml

@@ -125,6 +125,9 @@ spec:
             requests:
               cpu: 25m
               memory: 64Mi
+            limits:
+              # 7-day peak 459Mi (`:host` jobs run in this container); ~2.2x margin.
+              memory: 1Gi
           env:
             - name: DOCKER_HOST
               value: tcp://127.0.0.1:2375

workplans/RAPPS-WP-0019-product-neutral-forge-object-names.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Product-neutral forge object names (forgejo-gitea-* → forge-*)"
 domain: infotech
 repo: railiance-apps
-status: active
+status: finished
 flavor: refactoring
 owner: railiance-apps
 created: "2026-10-21"
@@ -120,9 +120,8 @@ Deploy each through its own path. When no consumer uses the old name, delete
 
 ```task
 id: RAPPS-WP-0019-T04
-status: todo
+status: done
 priority: low
-depends_on: [RAPPS-WP-0019-T02]
 state_hub_task_id: "0be013cc-6bc1-5e0e-8f06-e2deef0c919c"
 ```
 
@@ -134,7 +133,7 @@ name `forgejo-gitea`. Prefer "forge" wherever the concrete product is not meant.
 
 ```task
 id: RAPPS-WP-0019-T05
-status: todo
+status: done
 priority: low
 state_hub_task_id: "169aeda8-2f4a-5bef-9343-8ad367dde71a"
 ```
@@ -179,3 +178,15 @@ annotation. A cluster-wide scan afterwards found no workload or ConfigMap still
 naming `forgejo-gitea`. All three consumers answer healthz 200 on `forge-http`.
 The compatibility Service was deleted live, its manifest was removed, and HTTPS
 and SSH git still work.
+
+## Tooling and leftovers done — 2026-10-21
+
+**T04, tooling and docs:** railiance-forge now uses `FORGE_*` Makefile variables, `forge-status`, and an observer that targets `deploy/forge`. Its current docs use the new object names, and `docs/forgejo-on-railiance01.md` was updated here.
+
+**T05, Gitea-era leftovers removed.** None was referenced by a live path, and nothing named gitea runs in the cluster:
+- railiance-forge FORGE-WP-0009 (finished): the stale `gitea-deploy` / `gitea-ingress-deploy` targets, which would have overwritten production with July values, plus their values files, the ingress and the old CoulombCore release values.
+- railiance-platform: the `gitea-db` CNPG manifest and the db-deploy / db-status / db-shell / db-logs targets. They now refuse with a pointer to `forgejo-db-*`.
+- railiance-bootstrap and railiance-cluster: `helm/gitea-ssh-nodeport.yaml`.
+- the-custodian: the coulombcore Gitea package-push lockdown tooling.
+
+Kept on purpose: the data volume name `gitea-shared-storage`, the chart-imposed container names, and the namespace, release and hostname `forgejo` (deferred by the founder).