Validation: #257 jersey fields in PlayerProfileResponse

validation-257-2026-03-30 Doc

validation pass

Project

Validation: #257 jersey fields in PlayerProfileResponse

Date: 2026-03-30
PR: #259
Issue: #257
Verdict: PASS

Summary

PR #259 merged to main as commit 4cd0e1b. The kustomize tag in pal-e-deployments was updated to 4cd0e1b5 (confirmed by user). ArgoCD synced and the pod is now running the correct image. All four jersey fields are present in the PlayerProfileResponse schema and in the database.

Validation Checks

Check	Result	Evidence
PR merged	PASS	PR #259 merged as commit <code>4cd0e1b53d2dc60f0886b0d3d72bb578a5a5c46d</code>
Pod running correct image	PASS	Image: <code>harbor.tail5b443a.ts.net/basketball-api/api:4cd0e1b53d2dc60f0886b0d3d72bb578a5a5c46d</code>
Pod health	PASS	Pod <code>basketball-api-6c548b77bc-pvgw4</code> Running 1/1, healthz 200, no errors in logs. Prometheus scraping /metrics, Blackbox probing /docs -- all 200s.
OpenAPI schema	PASS	<code>PlayerProfileResponse</code> includes <code>jersey_option</code>, <code>jersey_size</code>, <code>jersey_number</code>, <code>jersey_order_status</code>. Also present in <code>AdminPlayerDetail</code>, <code>AdminPlayerItem</code>. <code>PublicPlayerResponse</code> correctly exposes only <code>jersey_number</code>.
Database columns	PASS	<code>players</code> table has all 4 columns: <code>jersey_option</code> (USER-DEFINED), <code>jersey_size</code> (USER-DEFINED), <code>jersey_number</code> (varchar), <code>jersey_order_status</code> (USER-DEFINED). Data present for existing players (defaults: empty/none).
Public API serialization	PASS	<code>GET /public/teams</code> returns players with <code>jersey_number</code> field (value <code>null</code> for players without jerseys assigned).

Previous Failure (resolved)

Initial validation on 2026-03-30 failed because the Woodpecker CI pipeline #259 skipped the update-kustomize-tag step. The kustomize tag was subsequently updated manually to 4cd0e1b5, ArgoCD synced, and the pod now runs the correct image.