changes-reportlisted

# Report Changes for a Period Produce one evidence-based account of what changed and why it matters, independent of commit and pull request boundaries. ## Required Input Require a date or period. Accept a single `YYYY-MM-DD` date, an explicit start and end date, or a clear relative period such as `today`, `this week`, or `last week`. If the user did not specify one, ask which date or period to report and stop. If it cannot be resolved to exact bounds, ask for a precise date or period and stop. Use the repository's local timezone unless the user specifies another timezone. Treat a single date as the half-open period from 00:00 on that date to 00:00 on the next date. Treat an explicit end date as inclusive by ending at 00:00 on the following date. Resolve calendar weeks from Monday at 00:00. End a relative period that includes the present, such as `today` or `this week`, at the current time; use full calendar bounds for completed periods such as `yesterday` or `last week`. Before inspecting changes, record the resolved start, exclusive end, timezone, and human-readable period label. Use those exact bounds throughout the report. ## Workflow 1. Confirm the repository and target branch. Use the current repository and branch when the user does not name them. 2. Find each merge, squash, and direct commit added to the target branch during the period, using first-parent history and committer time to define inclusion. Inspect the net change from the branch state immediately befo