CngxFilterChipContext

Per-chip override slot context. Consumers project an <ng-template cngxFilterChip let-option let-value="value" let-label="label"> to customize chip body decoration - icons, count badges, colour swatches, anything beyond the default text label.

Decoration-only semantics. The bridge ALWAYS wraps each option in <cngx-chip cngxChipInGroup [value]> itself; the slot only customizes what renders INSIDE that wrapper. Consumers do NOT redeclare selection wiring - it is handled by the bridge so the projected content survives Angular's *ngTemplateOutlet lexical-injector semantics (the projected template injects against the consumer's component, NOT the bridge's inner <cngx-multi-chip-group>, so a consumer-supplied cngxChipInGroup would fail to resolve CNGX_CHIP_GROUP_HOST).