v0.22.0

Frontmatter fields whose names start with _, # or @ are now ordinary fields. You
can filter, sort, project and update them like any other, and they survive a write
instead of being silently dropped. Only $ stays reserved — those fields are kept and
validated, but the query language keeps that prefix for its own operators.

iwe

Changed

• find, update, create --set and schema treat frontmatter fields starting with _, # or @ as ordinary fields and never drop them (previously hidden from output and stripped on update); $-named fields are kept and validated but cannot be targeted by --filter, --sort, --project, --set or --unset

iwec

Changed

• query results include frontmatter fields starting with _, #, @ or $ (previously omitted)

Library crates (liwe, diwe)

liwe

Changed

• Frontmatter fields whose names start with _, # or @ are ordinary fields — addressable, projected, sorted, validated, and kept on writeback (previously invisible to queries and dropped on update)
• A $-prefixed segment anywhere in a field path is now an InvalidPathSegment parse error (was a runtime miss for filter, sort and projection, and ReservedPrefixField for $set / $unset)
• prepend_frontmatter writes every key of the mapping (was dropping reserved-prefix keys)
• Projection output names may start with _, # or @; only $ is refused

Removed

• strip_reserved, is_reserved_segment and the query::frontmatter module — replaced by is_operator_segment in query::document
• ParseError::ReservedPrefixField