Overview:

A high level summary that describes this Task in a clear, concise way. Complete during New status.

As we remove static defaults, the runtime defaulting code may change from version to version to provide the best user experience.

We need to somehow prevent drift/bitrot of the field descriptions (in the CR schema) that describe what the semantics of a omitted values are. I.e. that they match the actual behaviour of the runtime defaulting code.

One way to do this would be to keep the description in a human-readable but structured form that could be read by a unit test. This unit test would automatically verify that they match the actual code behaviour.

Acceptance Criteria:

A list of specific needs or objectives that this task must deliver in order to be considered complete. Complete during Refinement status.