diary-entrylisted

# Diary Entry Write a single day's development diary entry for the current project, synthesized from the project's own aidd activity. The entry is saved as a markdown file under `.aidd/diary/` and is surfaced in the web control panel's per-project **Diary** tab and the global **Diary** page. ## Usage ``` diary-entry [--date <YYYY-MM-DD>] ``` - Zero args → write the entry for the current date. - `--date` → write the entry for the specified calendar date. ## Target File - `.aidd/diary/YYYY/MM/DD.md` (relative to the project root): one file per calendar day. - Parent directories (`YYYY/MM/`) are created if missing. - **Same-day overwrite is allowed.** Unlike the cross-project `devdiary-update`, this skill regenerates today's entry on demand (the web "Write today's entry" button re-runs it), and the files are git-versioned, so overwriting is safe and intended. Do not overwrite a _different_ day's entry; only write the file for the resolved target date. ## Frontmatter Schema (write exactly this shape) The web backend parses this frontmatter deterministically, so emit these keys verbatim. Quote string values with single quotes; escape an embedded single quote by doubling it (`''`). ```yaml --- date: 2026-06-12 # required; must equal the date in the file path (YYYY-MM-DD) project: aidd # required; the project directory name title: 'The Diary Lands' # required; evocative and specific; falls back to the H1 if omitted phase: Backend # optional; one of: Architecture | Fro