Today, OPA policy evaluation covers the fme_segment package (segment create/update) but does not extend to fme_segment_keys, which is the package used when adding users/keys to an already-existing segment. This creates a gap: policy checks can be bypassed by growing a segment incrementally after creation, since there's no enforcement point once a segment is live.

Ask: Add fme_segment_keys as a package covered by OPA policy evaluation, so that key/user additions to existing segments are subject to the same enforcement as segment creation — allowing customers to define org/project-scoped rules (e.g., blocking additions that would push a segment over a defined size threshold) rather than relying on a blunt account-wide cap.

Customer context: Customer wants to cap regular segments at 100 keys to prevent teams from building oversized segments (10K–100K range) through the standard segment-creation flow, where they should instead be using the Large Segments feature (>10K keys). This is specifically about regular segments, not Large Segments.