From 865ad48d367d91f52ef910f6e9cef41ecd6da416 Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 21 Oct 2026 21:08:12 +0200 Subject: [PATCH] FORGE-WP-0011: runner applied; server upgrade deferred pending sign-in reconciliation Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 276069@bnt-lap001 Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c --- WORK-RECORDS.md | 2 +- workplans/FORGE-WP-0011-forgejo-resource-requests.md | 10 +++++++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md index ccf91c5..f4ae9b9 100644 --- a/WORK-RECORDS.md +++ b/WORK-RECORDS.md @@ -33,7 +33,7 @@ | task | FORGE-WP-0010-T02 | done | — | workplans/FORGE-WP-0010-receive-scanner-budget.md | | task | FORGE-WP-0010-T03 | done | — | workplans/FORGE-WP-0010-receive-scanner-budget.md | | task | FORGE-WP-0011-T01 | done | — | workplans/FORGE-WP-0011-forgejo-resource-requests.md | -| task | FORGE-WP-0011-T02 | todo | — | workplans/FORGE-WP-0011-forgejo-resource-requests.md | +| task | FORGE-WP-0011-T02 | progress | — | workplans/FORGE-WP-0011-forgejo-resource-requests.md | | task | FORGE-WP-0011-T03 | todo | — | workplans/FORGE-WP-0011-forgejo-resource-requests.md | | task | FORGE-WP-0011-T04 | todo | — | workplans/FORGE-WP-0011-forgejo-resource-requests.md | | task | RFORGE-WP-0002-T01 | done | — | workplans/RFORGE-WP-0002-forge-resource-economics-evidence.md | diff --git a/workplans/FORGE-WP-0011-forgejo-resource-requests.md b/workplans/FORGE-WP-0011-forgejo-resource-requests.md index 901cca6..03caa2f 100644 --- a/workplans/FORGE-WP-0011-forgejo-resource-requests.md +++ b/workplans/FORGE-WP-0011-forgejo-resource-requests.md @@ -112,7 +112,7 @@ resources are in `after-render-resources.txt`. ```task id: FORGE-WP-0011-T02 -status: todo +status: progress priority: high state_hub_task_id: "d4162309-9869-5534-adf2-0417c40ce5d6" ``` @@ -228,3 +228,11 @@ a memory limit for the `runner` container (host-label jobs), removal of the two stale Failed pods from 66 days ago, and reconciling Helm release drift (rev 9 vs Deployment rev 14). The Prometheus `forgejo` request recording rule that returns no series is owned by rapp-telemetry. + +## Runner applied, server deferred — 2026-10-21 + +The founder ran a diff in their own terminal, rendered with the same inputs as `make forgejo-deploy` and compared with live. The agent reviewed only a redacted summary of it. + +- **Runner:** the diff showed only resources. Applied with `make forgejo-runner-deploy` (railiance-apps 4a1d653); the runner daemon and poller are up. +- **Server:** the Helm upgrade would also apply the NetKingdom sign-in declaration from railiance-apps 4d6a8dd (the `oauth` source and the `oauth2_client` app.ini section). That source was activated natively on 19 Oct (CUST-WP-0080 T42, source ID 1), and founder linking (T43) is still open. The founder chose to defer the server upgrade to a Helm reconciliation coordinated with the sign-in owners (RAPPS-WP-0016 / CUST-WP-0080 T43). Until then, the server requests declared in helm/forgejo-values.yaml are not live. +- **Naming:** `forgejo-gitea` and the `gitea` container come from the upstream chart `gitea-charts/gitea`, not the retired Gitea. Docs should say Forgejo. Renaming the live objects means recreating them, so it is a follow-up for a maintenance window. Evidence: the-custodian docs/evidence/2026-10-21-wave1-apply.md.