retro-analysislisted

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> # Retro Analysis Run a factual engineering retrospective over a defined time window. The purpose is to explain what changed, how the work happened, what quality signals say, what was learned, and what should improve next. This is an analysis workflow, not a performance-ranking or blame exercise. Use it manually at the end of a day, week, sprint, or release; on a recurring schedule; or when asked what was shipped, where time went, or how delivery quality is trending. When a specific implementation has just reached its goal, run this analysis before or alongside `olko:wrap-up` so the delivery audit and the broader retrospective remain distinct. ## Invocation Accept one of these arguments: - no argument or `7d`: the previous seven calendar days - `24h`: the previous 24 hours - `14d` or `30d`: the previous N calendar days - `compare` or `compare 14d`: compare the selected window with the immediately preceding window of equal length - `global`, `global 14d`: aggregate across discoverable repositories and agent sessions If the argument is invalid, print the accepted forms and stop. Do not silently choose a different window. Calendar windows are aligned to midnight in the operator's local timezone. A short hourly window may use a relative timestamp. State the resolved start, end, timezone, scope, and comparison window at the beginning of the report. Step 0, before collecting any evidence: resolve the dur