canned-prompts/workplans/CANP-WP-0007-wave2-resource-right-sizing.md

id	type	title	domain	repo	status	flavor	owner	topic_slug	created	updated	related	state_hub_workstream_id
CANP-WP-0007	workplan	Wave-2 resource right-sizing from the 2026-10-21 allocation review	agents	canned-prompts	finished	implementation	claude	practice	2026-10-21	2026-10-21	CUST-WP-0071 RESOURCE-WP-0008	da29d3a5-319b-525e-8401-e248ab95d8c7

CANP-WP-0007 — Wave-2 resource right-sizing from the 2026-10-21 allocation review

Receiving workplan in canned-prompts for the wave-2 request changes below.

Origin: the 2026-10-21 node allocation review (RESOURCE-WP-0008-T03, feeding CUST-WP-0071-T03). Per the founder's 2026-10-21 delivery interview (the-custodian/docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md) the small adjustments form wave 2: one receiving task per owner repo, applied later in a batch. Applying wave 2 needs a separate founder approval, so every cluster-write task here is a human-gated wait. This file changes no manifest.

Apply the reviewed request changes

id: CANP-WP-0007-T01
status: done
priority: medium
state_hub_task_id: "04a609e9-6ed6-5b2a-8bb8-6be1f0e1bbfa"

Values are pod-aggregate figures from the budget file (7-day window ending 2026-10-21T06:08Z). Limits stay unchanged unless stated.

Workload (ns/name)	Pods	CPU request	CPU limit	CPU p95/peak 7d (m)	Memory request	Memory limit	Mem p95/peak (Mi)	Throttle	Action
canned-prompts/canned-prompts	1	25m → 5m	500m	2.5/6.6	96Mi → 96Mi	384Mi	63.3/65.0	0.0	decrease

Source and container detail:

• canned-prompts/canned-prompts: Deployment canned-prompts, container canned-prompts, rapp-canned-prompts/manifests/runtime.yaml (25m/96Mi) — the deploy source lives in rapp-canned-prompts.

Prepared 2026-10-21 (wave-2 worker W1a; not applied). Live owner is client-side kubectl apply of rapp-canned-prompts manifests (last-applied annotation; no Helm, no ArgoCD). Change: rapp-canned-prompts 196b5df, manifests/runtime.yaml CPU request 25m → 5m; memory 96Mi and limits unchanged. Diff against live: runtime.yaml changes only resources.requests.cpu. The completed migration Job canned-prompts-schema-migration-0003 no longer exists live, so do not apply migration.yaml. Apply: kubectl apply -f rapp-canned-prompts/manifests/runtime.yaml.

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:

1. Map the pod-aggregate proposal onto the named container(s) in the source file; where a workload has several containers or pods, split by the per-pod figures in 2026-10-21-workload-usage.json and keep the sum at the proposed value.
2. Prepare the source change as a reviewed commit (no push, no sync) and record the before values here.
3. Apply only inside the batched wave-2 rollout, after founder approval, through the owner's normal deploy path (ArgoCD sync or documented helm/kubectl apply).

Verification: kubectl -n <ns> get pod -o jsonpath='{..resources}' shows the new requests; pods Ready with no new restarts or OOMKilled over 24h; for CPU decreases the throttle ratio and request latency stay at or below the 7d baseline; node request total drops by the expected delta.

Rollback: revert the source commit and re-sync/re-apply; the before values in the table above are the rollback target. Keep before/after kubectl get -o yaml captures as the receipt.

Applied — 2026-10-22 (CANP-WP-0007-T01)

Applied under the founder's wave-2 authorization (the-custodian docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md), after a full-render diff against live that showed resources only. Runtime manifest only (no migration Job re-run); Ready. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.