wrap-uplisted

# myna-wrap-up 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. Closes out the day. Reads today's daily note and vault state, writes an End of Day section, moves unfinished items forward, detects contributions, and saves behavioral corrections to Claude Code memory. The daily note becomes the complete record of the day: sync snapshots at top, user edits in the middle, wrap-up at the bottom. --- ## Step 1: Read Config and Today's Note Read `workspace.yaml`: - `vault.path` → vault root; Myna subfolder is always `myna` (hardcoded) - `timezone` → today's date - `user.role` → determines contribution categories Read today's daily note: `Journal/{YYYY-MM-DD}.md` If no daily note exists, create a minimal one (no sync snapshot) and proceed. The wrap-up section will note there was no morning sync. Also read: - Today's completed tasks: Grep `myna/` for `- \[x\]` with today's completion date - Today's meeting files: check `Meetings/` for files with today's date section - `Journal/contributions-{YYYY-W\d\d}.md` (ISO week, e.g. `contributions-2026-W18.md`) — to check for existing entries before adding new ones --- ## Step 2: Planned vs Actual Query open tasks across project files where `📅 {today}` — grep `Projects/` for `- \[ \].*📅 {today}`. These source-file due dates are what was "planned" for today. Do NOT attempt to read `### Immediate Attention` from the daily note — that section no