process-review-queuelisted

# myna-process-review-queue If vault_path is not in context, read `~/.myna/config.yaml` first. If the file does not exist, tell the user to run `/myna:setup` and stop. Processes pending review queue items. Writes approved items to their destinations with `[Verified]` tag. Logs all processed items to `ReviewQueue/processed/{YYYY-MM-DD}.md` for audit trail. **Does NOT handle `review-inbox.md`** — email triage is handled by /myna:email-triage. If the glob for queue files picks up `review-inbox.md`, skip it without parsing. ## Before You Start Read at session start: - `_system/config/workspace.yaml` — vault subfolder - `_system/config/projects.yaml` — project names for destination resolution - `_system/config/people.yaml` — person names for destination resolution Queue files: - `ReviewQueue/review-work.md` — ambiguous tasks, decisions, blockers, timeline entries - `ReviewQueue/review-people.md` — ambiguous observations, recognition - `ReviewQueue/review-self.md` — uncertain contribution candidates Audit trail: `ReviewQueue/processed/{YYYY-MM-DD}.md` --- ## Review Queue Entry Format The canonical entry format from foundations §2.10 is: ``` - [ ] **{proposed action}** Source: {where this came from} Interpretation: {what the agent thinks it means} Ambiguity: {why this needs review — what's unclear} Proposed destination: {where it would be written if approved} --- ``` Some producers also include a `Content:` field with the verbatim entry to write. This skill han