Problem
When YAML items in the same metadata block use different key orders, TSV rows can be written in each item's local key order instead of the final block header order.
This can shift values into the wrong columns, such as a watermark value appearing under fieldType.
Expected Behavior
All TSV rows should be written according to the generated block header order.
Missing optional fields should produce empty cells so later values stay aligned.
Reproduction
Create two fields in the same block with different YAML key orders, then convert to TSV.
Acceptance Criteria
- Rows align to the block header order.
- Missing optional fields are emitted as empty TSV cells.
- Regression test covers mixed key order within one block.
Problem
When YAML items in the same metadata block use different key orders, TSV rows can be written in each item's local key order instead of the final block header order.
This can shift values into the wrong columns, such as a
watermarkvalue appearing underfieldType.Expected Behavior
All TSV rows should be written according to the generated block header order.
Missing optional fields should produce empty cells so later values stay aligned.
Reproduction
Create two fields in the same block with different YAML key orders, then convert to TSV.
Acceptance Criteria