timeline-updatelisted

# timeline-update Someone wants to know when things land. This derives the answer from what the repo already holds and writes it to `docs/sprints/TIMELINE.md`. *(scale profile only.)* ## The rule that makes this trustworthy **State the evidence, or give no date.** A projection presented without its confidence is what teaches people to distrust plans - and once they do, they stop reading the timeline and start asking in meetings, which is the state this was meant to replace. So: below **three closed sprints** there is no measured throughput, and this must not present one. Three is not a magic number; it is the point below which one unusual sprint dominates the average, and the file says so rather than hiding it. What it does instead is the **cold-start mode** (ADR-029): if items carry `size`, describe the **shape** of what is left - "two `L`s and three `M`s remain, heavier than the last sprint's mix" - and say plainly that this is a ranking, not a date. ADR-029 is explicit that sizes are "never summed, never converted to numbers, and never fed into a projection", cold start included, so no duration is manufactured from a size letter under any circumstance - there is no such thing as an "estimated date" here, only a size-based read of how heavy the remaining work looks. If items carry no size either, report what is in flight and give no date at all. Both cold-start branches end the same way - **no date** - the only difference is whether the reader also gets a shape. **The