checkIssueRecordShape's block-spelled lapsed_at leg gates on the same-line value being empty, so it never sees the blocks entry that a block-scalar HEADER now populates: lapsed_at spelled as a header over an indented instant reports 'not an RFC 3339 instant' naming the header byte, instead of the block-spelled message its sibling shape gets. Both refuse the record, so this is message quality rather than a hole — the reader is sent to fix a format that is not the problem. Read the lapse leg through the same schemaRecord accessor the required-field check uses.

checkIssueRecordShape's block-spelled lapsed_at leg gates on the same-line value being empty, so it never sees the blocks entry that a block-scalar HEADER now populates: lapsed_at spelled as a header over an indented instant reports 'not an RFC 3339 instant' naming the header byte, instead of the block-spelled message its sibling shape gets. Both refuse the record, so this is message quality rather than a hole — the reader is sent to fix a format that is not the problem. Read the lapse leg through the same schemaRecord accessor the required-field check uses.

Grounds

• pursued: lapsed_at: | or >- over an indented instant reports the indented-block message on both categories; a format complaint naming the header byte would show it wrong