Replacement Omission Semantics Remain Unresolved

Context

The two entry points update the same record with different omission behavior. The existing product question remains the authority for choosing whether to align them.

Decision

HTTP replacement clears omitted optional values except confirmation and replaces lists, while domain replacement keeps supported omitted scalars pending Product's choice of a common contract.

Alternatives Considered

Make domain saving a complete replacement. This is recommended in the open question but would change domain caller expectations.

Preserve omissions in HTTP saving. Changing the replacement contract can hide incomplete requests and alter existing clients.

Consequences

Preparation must distinguish absent values from explicit clearing before adopting a shared write contract. This record keeps the disagreement open.