v0.30.0 — Minor release: a source file whose YAML frontmatter does not parse is read leniently and indexed instead of being skippe

Minor release: a source file whose YAML frontmatter does not parse is read leniently and indexed instead of being skipped (ADR 0052).

Fixed

• A memory or skill file whose YAML frontmatter does not parse is no longer skipped whole (ADR 0052). The most common cause is a plain-prose description: or title: containing : (Browser support: Chrome 114+), which YAML reads as a nested mapping and rejects. Strict YAML is still tried first; when it fails, the header is read one key: value line at a time (values keep their YAML type when YAML accepts them alone, otherwise the literal string; bare key: lines take their indented block as a list or nested mapping) and the file is indexed. The daemon logs frontmatter read leniently for <path> at INFO so the header can still be tidied. Headers that are not key: value lines at all are still reported on /health skipped_files and by memstem doctor.