fix(chart): use hasKey for boolean enabled to avoid Go template default trap

[chaodu-agent]

What problem does this solve?

PR #638 introduced enabled fields for cronjobs and the existing reactions.enabled already had the same pattern:

enabled = {{ .enabled | default true }}

In Go templates, default treats false as a zero value, so {{ false | default true }} returns true. This means users cannot disable cronjobs or reactions by setting enabled: false — the value is silently overridden to true.

Discovered during four-monk review of PR #638 by 覺渡法師 (Gemini).

Changes

File	What
charts/openab/templates/configmap.yaml	Replace {{ .enabled | default true }} with {{ if hasKey . "enabled" }}{{ .enabled }}{{ else }}true{{ end }} for both reactions.enabled and cron.jobs[].enabled
charts/openab/values.yaml	Clarify enabled comment: false = skip scheduling (job config is still validated at startup)

Testing

# cronjob enabled=false → renders false ✅
helm template test charts/openab \
  --set agents.kiro.cronjobs[0].schedule="0 9 * * 1-5" \
  --set-string agents.kiro.cronjobs[0].channel=123456789 \
  --set agents.kiro.cronjobs[0].message=hello \
  --set agents.kiro.cronjobs[0].enabled=false

# cronjob enabled not set → renders true ✅
helm template test charts/openab \
  --set agents.kiro.cronjobs[0].schedule="0 9 * * 1-5" \
  --set-string agents.kiro.cronjobs[0].channel=123456789 \
  --set agents.kiro.cronjobs[0].message=hello

# reactions enabled=false → renders false ✅
helm template test charts/openab \
  --set agents.kiro.reactions.enabled=false

Related

• Follow-up to PR fix(chart): align cronjob config with openab binary + add usercron support #638
• Note: validate_cronjobs() in src/cron.rs still validates disabled jobs at startup. This is a separate runtime concern — suggest opening a follow-up issue if the team wants enabled: false to also skip validation.

[github-actions]

⚠️ This PR is missing a Discord Discussion URL in the body.

All PRs must reference a prior Discord discussion to ensure community alignment before implementation.

Please edit the PR description to include a link like:

Discord Discussion URL: https://discord.com/channels/...

This PR will be automatically closed in 3 days if the link is not added.