Which required list a required parameter lands in
The rule
A required parameter is emitted into the input schema's required list if and only if it is not configurable, and into the config schema's required list if and only if it is not connectable.
What it means
Each derived required list waives itself in favour of the other side, not
in favour of the flag being true. A required parameter that is both
connectable and configurable is required in neither list: the input side
waives because the config form could supply it, and the config side waives
because a wire could — each treats the other as covering it, so required
ends up enforced nowhere. Turning off one of the two gates is what makes the
requirement bite, on whichever side is left.
Example
A required parameter value that the node type marks connectable only:
["value"][]Mark the same parameter connectable and configurable, and both lists come back empty: each path waives the other.