CORE-WP-0012-T01: record wave-2 preparation (not applied)

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

workplans/CORE-WP-0012-wave2-resource-right-sizing.md

@@ -43,6 +43,8 @@ Source and container detail:
 
 - `core-hub/rapp-core-hub`: three pods; `resources` in `railiance-apps/charts/core-hub/values.yaml` (chart default 250m/512Mi, which does not match the live 200m/896Mi total — find the deployed values override first). Production `hub.coulomb.social`: verify startup time and a full rollout under the lower request before keeping it.
 
+**Prepared 2026-10-21 (wave-2 worker W1a; not applied).** Live owner is Helm release `core-hub` (rev 33) from **rapp-core-hub** (`make deploy`), not railiance-apps. Change: rapp-core-hub `8c2fa02`, `values/production.yaml` request overrides, limits unchanged. Split of the 60m/288Mi aggregate by 7d per-pod p95: candidate `core-hub-api-candidate` (serves all routing groups) 50m/256Mi → 25m/128Mi; legacy `core-hub-api` 100m/512Mi → 15m/96Mi; `core-hub-api-repository-publisher` 50m/128Mi → 20m/64Mi. The full `make render` against live shows only `resources.requests` on the three Deployments (the baseline render before the change matched live exactly). Apply: `cd rapp-core-hub && make deploy` (helm upgrade --atomic --wait). All three pods roll (maxSurge 1, maxUnavailable 0). The pre-existing `test_render_is_deterministic_and_digest_pinned` failure (it expects the old forge URL) is unrelated to this change.
+
 Evidence: resource-control `docs/evidence/2026-10-21-node-allocation-review/2026-10-21-node-budget.md` (+ `.json`, commit `3d9b1bd`). Rule: CPU = max(floor, p95x1.5, peakx0.5) rounded up to 5m; memory request = 7d p95 working set x1.15 (only when the change is at least 64Mi).
 
 Steps: