Conformance mismatch: generated+default test omits default-only field despite write_defaults=true

[callumalpass]

Summary

settings.write_defaults is specified as default true, and create says default-only fields must be written when this is true. But one conformance test currently expects a default-only field to be omitted when the type also has a generated field.

Spec references

• 04-configuration.md (settings.write_defaults default true; must write default-only fields when true)
• 12-operations.md create step 8 (must write default-only fields when write_defaults is true)

Conflicting test

• tests/level-1/generated-default-interaction.yaml
  • Group: type with both generated and default on same field is valid
  • Test: create uses generated value not default
  • Current expectation: frontmatter_not_written: [category]

category is default-only (not generated). Under write_defaults: true (default), this should be written.

Proposed fix

Update the test to assert category is written (e.g. frontmatter_written: { category: "general" }).

This keeps generated-field precedence tests intact while aligning write behavior with the normative write_defaults semantics.