weekly-summarylisted

# myna-weekly-summary 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. Generates or updates the weekly summary. Each run appends a fresh `## Weekly Summary — {date}` section to the weekly note. Re-runs are additive — previous sections stay untouched. --- ## Step 1: Determine Target Week **No argument:** Default to the current week (Monday–Sunday, using today's date and timezone from workspace.yaml). **"last week":** Previous Monday–Sunday. **Specific date:** "week of April 7" → find the Monday for that week. Weekly note path: `Journal/{YYYY-W\d\d}.md` (e.g. `2026-W18.md`) --- ## Step 2: Read Config Read `workspace.yaml`: - `vault.path` → vault root; Myna subfolder is always `myna` (hardcoded) - `user.role` → determines framing of contribution categories --- ## Step 3: Read Existing Weekly Note Read the weekly note if it exists. Note any prior "Weekly Summary" sections for context. Each run always appends a full new summary section — do not skip or abbreviate because a prior section exists. --- ## Step 4: Gather Weekly Data Read in parallel: **Daily notes for the week:** Glob both `Journal/{YYYY-MM-DD}.md` and `Journal/Archive/Daily/{YYYY-MM-DD}.md` for each weekday — prior notes are archived to `Journal/Archive/Daily/` after each sync run. From each found daily note, extract: - End of Day "Completed" items (from wrap-up sections, if they exist) - End of Day "Not starte