Does FilamentPHP automatically merge nested validation rules into Repeater fields?

Goal: Determine whether FilamentPHP’s Repeater field automatically applies validation rules defined on its child (nested) fields when validating each repeater item, or whether those rules must be explicitly declared on the repeater schema via a ‘validation’ attribute.

Uncertainty: The official documentation does not specify if nested validation rules are flattened into the repeater’s rule set, and anecdotal reports indicate inconsistent behavior across versions, leading to silent validation failures or unexpected error messages.

Questions: Does FilamentPHP currently merge nested validation rules into the repeater’s validation set? If merging does not occur, what is the recommended method to ensure nested rules are enforced? Is there a configuration flag or attribute that enables automatic rule merging for nested repeater fields?