mif-docs v0.9.4

[0.9.4] - 2026-08-04

Added

• The validate-plugin gate now inspects commands/**/*.md and
  agents/**/*.md frontmatter (#186) with dedicated ajv schemas
  (COMMAND_FRONTMATTER_SCHEMA, AGENT_FRONTMATTER_SCHEMA), enforces
  agent name/basename agreement, and accepts a plugin-root override
  (CLI argument or VALIDATE_PLUGIN_ROOT, both empty-safe) so tests can
  target fixture trees.

Fixed

• MARKETPLACE_SCHEMA accepts the string-shorthand plugin source form
  (#183) alongside the discriminated object form, matching every real
  marketplace manifest in the org.
• Malformed plugin.json or marketplace.json now surface as structured
  validation errors with exit 1 (#182) instead of crashing the
  validate-plugin gate with a bare parse stack trace.
• Closed the gate-coverage gap between the content-based ADR carve-out and
  the directory-scoped adr-smadr CI job (#209): scripts/lib/corpus.mjs
  now fails closed on a type: adr document the adr-smadr job cannot see
  (outside docs/adr/, or nested below it — the job's '*.md' pattern is
  non-recursive), instead of silently dropping it from the mif-validate
  corpus and leaving it validated by nothing.
• Made the repo's own five ADRs (docs/adr/0001-0005) conform to the
  adr genre skill they ship with (#203): each now carries type: adr,
  a lifecycle status:, and the full structured-MADR frontmatter, so
  audit-v2's immutable-ADR policy and the structured-madr oracle
  routing engage on them. scripts/lib/corpus.mjs gained a content-based
  ADR carve-out (listAdrDocs) that keeps type: adr documents out of
  the mif-validate corpus, and the adr-smadr CI job now validates
  docs/adr/ in both smadr (strict) and mif (level 3) modes.