Bug Report: enrichGroupParticipantsFromContacts Schema Inconsistency

Summary

The channels.bluebubbles.enrichGroupParticipantsFromContacts configuration field shows inconsistent behavior between schema lookup and config validation.

Description

Observed Behavior

1. openclaw config.schema.lookup channels.bluebubbles shows enrichGroupParticipantsFromContacts as a valid field with type: boolean and required: true
2. However, openclaw config set channels.bluebubbles.enrichGroupParticipantsFromContacts false fails with: Config validation failed: channels.bluebubbles: Unrecognized key: "enrichGroupParticipantsFromContacts"
3. openclaw doctor --fix also reports this as an "Unrecognized key" problem

Expected Behavior

Either:

• The field should be accepted by config validation (since it's in the schema), OR
• The field should not appear in schema lookup

Steps to Reproduce

# 1. Check schema - shows field as valid
openclaw config.schema.lookup channels.bluebubbles

# 2. Try to set the field - fails
openclaw config set channels.bluebubbles.enrichGroupParticipantsFromContacts false
# Error: Config validation failed: channels.bluebubbles: Unrecognized key: "enrichGroupParticipantsFromContacts"

# 3. Run doctor --fix
openclaw doctor --fix
# Reports: channels.bluebubbles: Unrecognized key: "enrichGroupParticipantsFromContacts"

Environment

• OpenClaw Version: 2026.3.28 (f9b1079)
• Node Version: v24.14.0
• OS: macOS 12 (Monterey)
• Shell: zsh

Schema Lookup Output

{
  "key": "enrichGroupParticipantsFromContacts",
  "path": "channels.bluebubbles.enrichGroupParticipantsFromContacts",
  "type": "boolean",
  "required": true,
  "hasChildren": false
}

Additional Context

This causes issues when running third-party install scripts (like kimi-claw) that trigger gateway restarts. The plugin appears to inject this field, but then config validation fails.

The documentation at docs/channels/bluebubbles.md also documents this field:

channels.bluebubbles.enrichGroupParticipantsFromContacts: On macOS, optionally enrich unnamed group participants from local Contacts after gating passes. Default: false.

Root Cause Analysis

It appears there are two separate schema definitions:

1. Query/Documentation schema (returned by config.schema.lookup) - includes enrichGroupParticipantsFromContacts
2. Validation schema (used by config set and doctor) - does NOT include this field

This inconsistency needs to be resolved by either:

• Adding the field to the validation schema
• Removing it from the documentation schema

Workaround

Currently, users must manually remove this field from ~/.openclaw/openclaw.json after running install scripts that trigger gateway restarts.

Related: This affects the BlueBubbles channel's contact enrichment feature as documented in docs/channels/bluebubbles.md.