Per-field merge of a data source's run/publish options against the project's
dataSourceDefaults. A plain object spread ({ ...defaults, ...overrides }) is not
used because a key present on overrides but explicitly undefined — which only a
programmatic (non-YAML) caller can produce, since the JSON schema rejects
null/undefined — would wipe a set default; ?? instead falls back to the default for
any field the data source leaves undefined. Object/array fields (schedule,
recommendation, filterExpressions) are still not deep-merged: a value present on
overrides fully replaces the matching default.
Per-field merge of a data source's run/publish options against the project's
dataSourceDefaults. A plain object spread ({ ...defaults, ...overrides }) is not used because a key present onoverridesbut explicitlyundefined— which only a programmatic (non-YAML) caller can produce, since the JSON schema rejects null/undefined — would wipe a set default;??instead falls back to the default for any field the data source leavesundefined. Object/array fields (schedule,recommendation,filterExpressions) are still not deep-merged: a value present onoverridesfully replaces the matching default.