log-reviewlisted

# log-review — a period of logs into accomplishment statements Reads the daily files `/pm:log` wrote over a period and produces the thing those files cannot be used as directly: a short list of what you accomplished, phrased so it survives being pasted into a self-review or a CV. It works from what is on disk. It does not go back to the tracker, and it does not go to chat — if something is not in the logs, it did not get captured, and the honest answer is that it is missing. **The judgement is yours, not the skill's.** A daily log knows that a status changed; it does not know whether that mattered, how much of it was your work, or what it can be measured by. Those three things are asked, never assumed. A period with no answers produces no statements, which is a correct outcome. ## Principles - **Only what the files support.** Every statement traces to entries in the period. Nothing is added from memory or inference. - **Numbers come from the user.** If no figure is given, the statement carries `log.review.unknown_metric` rather than a fabricated one. A vague number is worse than a missing one — it will be read back as fact in a room where it can be challenged. - **Quotes stay quotes.** Anything from the `What others said` section is carried across verbatim with its link. Never paraphrased into praise. - **Existing entries are not rewritten.** The highlights document accumulates. A rerun of the same period updates only what the user changes in the preview. - **One item at