handoff-listlisted

# Handoff: List Give the user a quick, scannable overview of every handoff they have parked, so they can decide what to pick up next. ## Step 1 — Find the handoffs Look in `.handoffs/` in the project root for files named `handoff-NNNN.md`. If the directory does not exist or is empty, tell the user there are no saved handoffs yet and mention they can create one with `handoff-create`. Stop there. ## Step 2 — Read each handoff's summary For every file, read the frontmatter (`handoff`, `title`, `created`) and the `<handoff-summary>` block. The summary is written to be self-contained — that is the part the user wants to see. If a file's frontmatter or summary cannot be parsed, mark it with `⚠ malformed` and continue listing the rest. ## Step 3 — Present the overview Show the handoffs ordered by number. For each one, give the number, title, created date, and the summary in the user's own language if they are not writing in English. (Handoff files are stored in English; translate summaries into the user's language for display only.) A compact table works well when there are several: | # | Title | Created | Summary | |------|-------------------------------|------------|----------------------------------| | 0001 | Add rate limiting to the API | 2026-05-12 | <one-line gist of the summary> | | 0002 | Migrate config to TypeScript | 2026-05-18 | <one-line gist of the summary> | If there are only one or two handoffs, a