Replace configuration at the read version with explicit clearing rules

Context

Administrators need version checks and deliberate clearing semantics when replacing configuration.

Decision

Retain versioned replacement and explicit clearing behavior; propose complete-payload enforcement as additional work.

Alternatives Considered

Introduce partial configuration updates. Current configuration operations replace records; patch behavior would need a distinct contract.

Continue defaulting omitted replacement properties. Omitted properties can reset or clear values; refusing them is proposed rather than established.

Consequences

The current schemas still allow some omitted properties. Product must decide whether to adopt the separately approved CRM approach for Commerce.