Helm: discord.enabled not set on upgrade from 0.7.6 causes CrashLoopBackOff

[thepagent]

Parent: #382

Problem

Upgrading from 0.7.6 → 0.7.7-beta.1 with helm upgrade --reuse-values causes CrashLoopBackOff:

Error: failed to parse /etc/openab/config.toml: missing field `discord`

The new chart added discord.enabled: true as a default, but --reuse-values preserves the old user-supplied discord block which does not include enabled. The template condition and ($cfg.discord).enabled ($cfg.discord).botToken evaluates to false, so [discord] is omitted from config.toml entirely.

Workaround

helm upgrade openab openab/openab --version 0.7.7-beta.1 --reuse-values \
  --set agents.<name>.discord.enabled=true

Suggested fix

Option A: Default discord.enabled from presence of botToken in the template (if botToken is non-empty, treat as enabled)
Option B: Add migration note to NOTES.txt / release notes
Option C: Make the binary tolerate missing [discord] section when discord is Option<DiscordConfig> in config.rs (it already is, so this may be a TOML parsing issue with empty sections)

[github-actions]

Thanks for the report! It looks like this issue was created without a template and is missing some required fields. Please add one of the following labels: bug, feature, documentation, or guidance, then edit this issue to include the matching template fields — the incomplete label will be removed automatically.