[Security][High] Redact Communication remoteParty in webhook payloads

[BechsteinDigital]

Severity

High

Problem

Communication call events serialize the remote telephone number under remoteParty. The plugin manifest declares no sensitive fields for this payload, and the default sensitive-field registry does not include remoteParty. Consequently, webhooks can transmit the number even when IncludeSensitiveData=false.

The documentation describes other field names and therefore does not protect the actual emitted schema.

Evidence

• custom/static-plugins/Communication/src/Application/Calls/CallBusinessEvent.cs:65
• custom/static-plugins/Communication/registry.json:1
• src/Core/Application/Webhooks/SensitivePayloadFieldRegistry.cs:15
• src/Core/Application/Webhooks/WebhookDispatcher.cs:60
• docs-site/guides/fundamentals/registry-manifest.md:121

Acceptance criteria

• The actual call-event schema declares every telephone-number field as sensitive.
• Default webhook delivery masks remoteParty.
• Sensitive delivery remains possible only through the explicit privileged setting.
• A test dispatches a real CallBusinessEvent through the production minimizer.
• Schema and documentation use the same field names.