Bump agent-controller chart to 0.4.0 (0.3.0 was overwritten by #198)

[DavidNic11]

Bumps charts/agent-controller from 0.3.0 to 0.4.0 and regenerates Chart.lock.

Why this is a fix, not housekeeping

#198 added the temporal-engine subchart as a new dependency but left version: 0.3.0 alone. release.yml's own comment explains the consequence:

# Charts are pushed under their Chart.yaml `version` -- OCI tags are
# mutable, so pushing again at the same version overwrites that tag
# rather than creating a new one. Bump `version` in the relevant [chart]

So the published 0.3.0 tag was overwritten with a chart that has a dependency the original 0.3.0 didn't. Anyone who pinned --version 0.3.0 now resolves something materially different from what they pinned.

That was my omission in #198, and it's the reason this is worth doing promptly rather than folding into a later PR.

Minor, not patch

A new subchart is a feature. It's also additive — temporal-engine.enabled defaults to false, so 0.4.0 renders identically to what 0.3.0 originally rendered unless someone opts in. Nobody upgrading gets new behaviour by accident.

Chart.lock was stale for the same reason

It never listed temporal-engine, so its digest no longer matched Chart.yaml. Regenerated with helm dependency update, which also refreshed the open-webui / nats entries it locks. Same three-file shape as the last version bump in this repo (b756db6: umbrella Chart.yaml, Chart.lock, and the subchart that changed).

Verified

• helm package → agent-controller-0.4.0.tgz
• helm lint clean
• the downloaded dependency tarballs are gitignored (.gitignore:32) and were removed rather than committed

Not bumped here

The agent-orchestrator subchart, which is unchanged on main — #197 changed the app, not its chart. The draft that enables the engine (#199) does modify it, so that PR needs its own bump of both charts when it lands. Flagged there rather than pre-empted here.

🤖 Generated with Claude Code

https://claude.ai/code/session_018Uj1SJ41DJJ8woZM7fd3DQ