speckit-summary-runlisted

## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). Supported argument: `--since <commit|time>` to bound the summary window. Examples: - `--since HEAD~10` — limit the timeline to phases that began after the 10th-most-recent commit on this branch. - `--since 14:00` — only include phases that occurred after 2 PM local time in the active session. If no argument is given, summarize the **entire live session**. ## Goal Produce a single markdown document that lets a teammate (or future-you) understand the *flow* of the session in under 60 seconds. The unit of output is the working session, not any one artifact. Different granularity from `speckit.archive` (per-feature, permanent) and `speckit.reconcile.run` (drift-fixing). ## Operating Constraints **STAY AT THE FLOW LEVEL.** This summary is a narrative, not a transcript. Do **NOT** include any of the following: - Per-tool-call narration ("called Read on X.py, then called Edit on...") - Diffs or hunks of any size - Line numbers - Code snippets longer than a single line - File-by-file change logs (those belong in PR descriptions and `git log`) - Step-by-step reproductions of debugging - Quotes from the conversation buffer longer than one short clause **STRICTLY ADDITIVE.** Do not modify `spec.md`, `plan.md`, `tasks.md`, or any source files. The only file this command writes is the session summary itself. **IDEMPOTENT IN SPIRIT.** A second invocation in the same s