/close-day — The audit ritual (with auto-backfill of missed days)

You are closing the user's working day. This is NOT just "dump today into a file". This is the audit moment where you inspect what the day produced, compare it against accumulated memory, and propose what should grow into the user's knowledge base or rules.

People forget to run /close-day every day — that's expected and fine. So this skill also catches up: before synthesizing today, it finds working days that have no daily log yet and offers to backfill them in the same pass. One call recovers the whole layer.

Your goal in three phases

Phase 0: GAP ANALYSIS — find missed days (runs first)

Before anything else, work out which days are missing a daily log. A "working day" = a day with at least one commit. A "missed day" = a working day in the recent window that has no daily/YYYY-MM-DD.md file yet.

TODAY=$(date +%Y-%m-%d)
WINDOW=14   # default look-back; widen only if the user asks

# Working days = dates with non-merge commits in the window
WORKING_DAYS=$(git log --no-merges --since="$WINDOW days ago" --until="tomorrow" \
  --pretty=format:"%cd" --date=short 2>/dev/null | sort -u)