create-observe-run-reportlisted

# Create an Observe-Run Report An observation run that cannot see the previous ones starts blind every time. This skill defines the file contract that gives the ODD loop its memory: reports live **in the observed repository**, so git versions them, PRs review them, and every user of the repo shares them — no side-channel storage, nothing opaque. The report is also the loop's **only durable artifact**: the raw telemetry behind it lives in a volume-less container that any `odd_stack_reset` — from this project or another on the same machine — destroys irreversibly. A question that only occurs at verify time is unanswerable unless its numbers were recorded at observe time: when in doubt, record the number. ## Where reports live ```text <observed-repo-root>/.odd/observe-run-reports/YYYY-MM-DD-HHmm-<run_name>.md ``` - `YYYY-MM-DD-HHmm` is the run's **UTC** start time — timestamped to the minute so two same-day runs never collide, and so a plain directory listing sorts chronologically. Compute it, `date:` and `window` with `date -u`, never from the local clock: a session that crosses local midnight while UTC has not names the wrong day. - `<run_name>` is a short kebab-case slug derived from what the run analyzed (e.g. `checkout-latency-sweep`, `orders-post-hoc-errors`). Name the content, not the date — the date is already in front. - A **verification run** — a run that replays a stored report's protocol: an observation report's measurement protocol, or an instru