bug: image.tag hardcoded in values.yaml causes version mismatch after helm upgrade

[JARVIS-coding-Agent]

Summary

charts/openab/values.yaml has image.tag hardcoded to a commit hash (94253a5), which prevents Helm from using the appVersion defined in Chart.yaml. This causes the deployed pod to run an outdated binary even after upgrading the Helm chart.

Impact

The running OpenAB instance reports version 0.1.0 (from the old commit) instead of the expected 0.7.0, because the image tag never changes on helm upgrade.

Reproduction Steps

1. Deploy OpenAB using the Helm chart:

   helm upgrade --install openab ./charts/openab

2. Verify the deployed image:

   kubectl get deployment openab-kiro -o jsonpath="{.spec.template.spec.containers[0].image}"
   # Output: ghcr.io/openabdev/openab:94253a5

3. Check the running version:

   kubectl exec deployment/openab-kiro -- openab --version
   # Output: 0.1.0 (expected: 0.7.0)

4. Note that Chart.yaml has appVersion: "0.7.0-beta.1" but the pod still uses the hardcoded commit hash image.

Root Cause

In charts/openab/values.yaml:

image:
  repository: ghcr.io/openabdev/openab
  # tag defaults to .Chart.AppVersion
  tag: "94253a5"          # ← hardcoded, overrides appVersion fallback

The comment says it defaults to appVersion, but since a value is explicitly set, the template never falls back.

Fix

Set image.tag to an empty string so the template uses .Chart.AppVersion:

image:
  tag: ""