myna-dev-consistencylisted

# Myna Dev Consistency QA pass for format consistency across the Myna vault. Finds the #1 source of real bugs: multiple skills writing to the same vault destination with diverging formats. Reads canonical formats from foundations.md and the conventions steering skill, then reads each writing skill's actual format instructions and compares them. Reports exact divergences — which skill is wrong and what the correct format is. Report only — does NOT modify skill files. ## Arguments $ARGUMENTS Parse for: - No arguments: check all shared destinations - Destination name(s): e.g., `timeline`, `contributions`, `review-queue` - Skill path(s): check named skills against canonical formats - `--uncommitted`: only skills with uncommitted changes ## Process ### Step 1: Read Canonical Sources - `docs/design/foundations.md` — canonical entry formats for all shared destinations - `agents/skills/myna-steering-conventions/SKILL.md` — authoritative entry format patterns - `agents/skills/myna-steering-vault-ops/SKILL.md` — vault path patterns ### Step 2: Identify Writing Skills Per Destination Use the authoritative map from `docs/design/architecture.md`: - Project timeline entries → myna-capture, myna-process-messages, myna-process-meeting - Person observations → myna-capture, myna-process-messages, myna-process-meeting - Person recognition → same - Contributions log → myna-capture, myna-process-messages, myna-process-meeting, myna-wrap-up, myna-self-track - Task entries → myna-capture, m