diff --git a/docs/evidence/2026-10-21-wave1-apply.md b/docs/evidence/2026-10-21-wave1-apply.md
index 9d1138ef..b941e45e 100644
--- a/docs/evidence/2026-10-21-wave1-apply.md
+++ b/docs/evidence/2026-10-21-wave1-apply.md
@@ -17,7 +17,7 @@ order STATE-WP-0099 requires.
 | 4 state-hub-db none→70m/416Mi | 3605m (90%) | 10144Mi | +70m |
 | 5 rapp-telemetry (Prometheus 205m/1152Mi, Grafana 35m/512Mi, 10d retention) | — | — | +10m / +880Mi |
 | 6a Forgejo runner (dind 100m/432Mi, runner 25m/64Mi) | 3740m (93%) | 11520Mi (72%) | +125m / +496Mi |
-| 6b Forgejo server | deferred | | (+200m / +976Mi when applied) |
+| 6b Forgejo server (Helm reconciliation, revision 10) | 3840m (96%) | 12496Mi (78%) | +100m effective / +976Mi |
 
 Wave 1 nets out as the review predicted. The node is now at 93% of CPU
 requests. Further increases, including the deferred Forgejo server and routine
@@ -62,3 +62,16 @@ state-hub release surges, depend on the wave-2 reductions
 - Forgejo Helm reconciliation together with the sign-in owners. Retire the
   legacy "gitea" naming when convenient (the upstream chart name, not the retired
   Gitea server).
+
+## Forgejo server reconciliation (later the same evening)
+
+The founder ran the final `helm upgrade` of `make forgejo-deploy` after a
+redacted diff review. The prerequisite manifests matched live, and the
+`eso-deploy` chain was skipped deliberately. Results:
+- Helm revision 10 now matches live.
+- The server requests 200m/1104Mi with a 1536Mi limit, and is healthy.
+- The NetKingdom sign-in source is unchanged: the chart took its update path
+  with identical values. The redirect still uses S256 PKCE, the HTTPS callback
+  and a single scope list.
+
+Details: railiance-forge FORGE-WP-0011-T03. Wave 1 is complete.
diff --git a/workplans/CUST-WP-0071-measured-workload-sizing-and-weekly-review.md b/workplans/CUST-WP-0071-measured-workload-sizing-and-weekly-review.md
index 74010004..d9e1e6da 100644
--- a/workplans/CUST-WP-0071-measured-workload-sizing-and-weekly-review.md
+++ b/workplans/CUST-WP-0071-measured-workload-sizing-and-weekly-review.md
@@ -609,3 +609,11 @@ The node is at 3740m of 4000m CPU (93%) and 72% of memory, as budgeted. T03 and
 stay open until the wave-2 receiving tasks reduce requests (routine state-hub
 releases need that headroom: STATE-WP-0099-T06) and the effects are observed
 over a representative window (RAPP-TELEMETRY-WP-0002-T05 re-measures after 7 days).
+
+### Forgejo server reconciled — 2026-10-21 evening
+
+After the founder's redacted diff review, the Forgejo server Helm upgrade ran
+(revision 10). Helm and live now match, the NetKingdom sign-in is unchanged, and the
+server requests 200m/1104Mi. **Wave 1 is complete.** The node is at 3840m CPU (96%)
+and 78% memory, so wave 2 is now the precondition for any further increase or for
+routine state-hub release surges.