bug(helm): chart rejects "multibot-mentions" for allowUserMessages despite binary supporting it (#464)

[brettchien]

Description

Helm chart template rejects allowUserMessages: "multibot-mentions" even though the openab binary supports it since #464. The validation block in charts/openab/templates/configmap.yaml was not updated when #464 added the new enum variant.

Binary side (works):

// src/config.rs
pub enum AllowUsers {
    #[default]
    Involved,
    Mentions,
    MultibotMentions,   // added in #464
}

// deserializer accepts "multibot-mentions" or "multibot_mentions"

Both src/discord.rs and src/slack.rs have gating branches that handle AllowUsers::MultibotMentions, so the feature is fully implemented in the binary.

Chart side (blocks):

{{- /* charts/openab/templates/configmap.yaml:47 (Discord) */ -}}
{{- if not (has $cfg.discord.allowUserMessages (list "involved" "mentions")) }}
{{- fail (printf "agents.%s.discord.allowUserMessages must be one of: involved, mentions — got: %s" $name $cfg.discord.allowUserMessages) }}
{{- end }}

Same hardcoded list at :80 for Slack.

Any user who follows the new docs in docs/discord.md § Multi-Bot Setup and sets allowUserMessages: "multibot-mentions" gets blocked by this check before the pod ever starts.

Steps to Reproduce

cat > /tmp/values.yaml <<'EOF'
agents:
  kiro:
    discord:
      allowUserMessages: "multibot-mentions"
EOF

helm upgrade --install openab openab/openab --version 0.7.8-beta.7 -f /tmp/values.yaml

Fails with:

Error: UPGRADE FAILED: execution error at (openab/templates/configmap.yaml:48:8):
agents.kiro.discord.allowUserMessages must be one of: involved, mentions — got: multibot-mentions

The same failure happens for agents.<name>.slack.allowUserMessages.

Expected Behavior

The Helm chart should accept "multibot-mentions" (and the snake-case alias "multibot_mentions" that the Rust deserializer also accepts) for both discord.allowUserMessages and slack.allowUserMessages.

Fix is one line in two places — add "multibot-mentions" to the allow list:

{{- if not (has $cfg.discord.allowUserMessages (list "involved" "mentions" "multibot-mentions")) }}

and the corresponding trailing comment (| multibot-mentions: …) so helm template output documents the new mode.

Environment

• Chart: openab-0.7.8-beta.7
• App: openab-0.7.8-beta.7
• Repro: helm upgrade --install ... from either Helm repository or local chart directory

Screenshots / Logs

$ helm upgrade --install openab openab/openab --version 0.7.8-beta.7 -f values.yaml
Error: UPGRADE FAILED: execution error at (openab/templates/configmap.yaml:48:8):
execution error at (openab/templates/configmap.yaml:48:8):
agents.claude.discord.allowUserMessages must be one of: involved, mentions — got: multibot-mentions

[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.

[brettchien]

@thepagent could you apply the bug label to this issue? Body follows the bug.yml template sections (Description / Steps to Reproduce / Expected Behavior / Environment / Screenshots / Logs). Adding the label should auto-clear the incomplete label via the openab-issue-check workflow.