Sync develop → main for v1.5.1 chart release

[saadqbal]

Promote develop → main for the v1.5.1 chart release

Ships the ingestor greenfield-baseline bump to customers. On merge, create a GitHub Release v1.5.1 to trigger release-helm-chart.yaml (packages + publishes to the gh-pages helm repo).

What this carries

Exactly one commit — the baseline bump (#228, toward #227):

File	Change
client/values.yaml	images.ingestor.digest 0.3.2 (d361fa77…) → 0.3.6 (dfdaa7e6…, multi-arch)
client/Chart.yaml	version + appVersion 1.5.0 → 1.5.1

Why

A customer (Opentarget) is stuck on ingestor v0.3.2, hitting data-ingestors#150 ("empty cells flagged as non-numeric", fixed in 0.3.3). main currently publishes chart 1.5.0, whose pinned baseline is v0.3.2 — so fresh installs and helm upgrade keep landing there. Bumping the baseline to v0.3.6 means fresh installs and upgrades land on the fixed image.

Precedent: the previous baseline bump (v0.3.1→v0.3.2) shipped as chart v1.4.4 the same way.

After merge

1. Create GitHub Release v1.5.1 (tag on main) → publishes chart to https://tracebloc.github.io/client.
2. Customer: helm repo update && helm upgrade … tracebloc/client → lands on v0.3.6.

Toward #227. Release-gated promotion — fr-gate + second approver (no self-approve).

🤖 Generated with Claude Code

---

Note

Low Risk
Helm values and chart version only; no template or runtime logic changes, with a targeted image digest bump for a known customer regression.

Overview
Releases client chart v1.5.1 by promoting the ingestor greenfield baseline from v0.3.2 to v0.3.6 (images.ingestor.digest in client/values.yaml), with matching version / appVersion bumps in client/Chart.yaml.

Fresh installs and helm upgrade will seed jobs-manager’s INGESTOR_IMAGE_DIGEST with the v0.3.6 multi-arch image so ingestion Jobs no longer land on the stale 0.3.2 pin (including the empty-cell / NULL handling fixes called out in the values comments). The floating images.ingestor.tag (0.3) is unchanged; ongoing drift is still handled by image-refresh.

^{Reviewed by Cursor Bugbot for commit 6f2a70a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[LukasWodka]

👋 Heads-up — Code review queue is at 10 / 8

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

• client#215 — Post-install self-verification of CLI usability (#738) · author: @LukasWodka · no reviewer assigned
• client#223 — test(charts): add helm-unittest suite for requests-proxy-service template · author: @saadqbal · no reviewer assigned
• client#224 — fix(Wire SINGLE_NODE flag: chart default from hostPath.enabled + installer sets it #222): wire SINGLE_NODE — chart default from hostPath.enabled + installer · author: @saadqbal · no reviewer assigned
• client#225 — fix(mysql): probe over TCP so a moved socket can't kill a healthy DB · author: @LukasWodka · reviewer: @saadqbal
• client#229 — fix(proxy): make all egress workloads proxy-aware (wire the dead HTTP_PROXY_* values) · author: @LukasWodka · reviewer: @saadqbal
• client-runtime#93 — fix(chore: revert default CODEOWNERS (back to author-picks-reviewer) #92): gate GPU→CPU pending fallback to single-node clusters · author: @saadqbal · no reviewer assigned
• data-ingestors#169 — feat: add token_classification (NER/POS) ingestion · author: @shujaatTracebloc · reviewer: @divyasinghds
• design-system#38 — feat(molecules): add ButtonGroup + InputButtonCombo · author: @waqaskhanroghani · reviewer: @saadqbal
• tracebloc-client#355 — fix(object_detection): scale RCNN targets to pixel space · author: @shujaatTracebloc · reviewer: @divyasinghds

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)