v0.2.1

Patch release of megabrain.md — three conformance-checker fixes, all false positives found while upgrading a heavily customized 0.1.0 instance. No conformance requirement changes; no migration pack, and none needed.

What's in this release

The megabrain specification, v0.2.0 (unchanged — attached: SPEC.md)

The fixes are entirely in the managed checker (scripts/megabrain.py):

• Block scalars in frontmatter — the bundled minimal YAML parser now consumes literal (|) and folded (>) block scalars instead of reporting unexpected indentation on valid YAML. A manifest using note: >- for a long declaration no longer fails [M-4] — and no longer masks every downstream check behind an unparseable manifest
• Non-Markdown entity paths — a declared entity path that is not a .md file (an Obsidian .base derived view, say) is no longer treated as a note. The spec defines a note as a Markdown file with YAML frontmatter, so the frontmatter and filename checks ([S-1], [S-6], [S-16]) were unsatisfiable for such files
• Directory coverage in [E-1] — undeclared-directories now flags the specific notes no declaration covers, rather than any directory that isn't itself a declared path. A directory whose notes are all individually declared — a file-path entity next to a declared subdirectory — is no longer reported, and the finding names the offending files

Upgrading

Instances at 0.2.0 get the fixed checker on their next upgrade through ordinary managed-file replacement — there is nothing to do now. Instances mid-bootstrap from 0.1.0 should fetch this release rather than v0.2.0: the pre-migration conformance check (step 5) runs from the release, and 0.2.0's checker can block a conforming instance.

Full Changelog: v0.2.0...v0.2.1