mdflow: the ./flows agent roster

Every repo deserves an agent roster. ./flows holds one markdown agent per job: code review, release notes, issue triage. Flows are diffable in PRs, provable with md eval, and new teammates (human or AI) learn how the project works by reading them.

A flow is one markdown file. Frontmatter is config. The body is the prompt. mdflow spawns the right engine CLI and passes everything through.

First action

Run md doctor --json before changing a project. Its stable diagnostic codes and effect-labelled next actions are authoritative for the current checkout. Do not infer project proof, engine availability, hook support, or evolution readiness by scraping prose when doctor reports it directly.