Changelog Scout

1. 1.Crawl the provided changelog page and grab raw release headings.
2. 2.Extract dates, version tags, and text for every distinct change.
3. 3.Flag breaking changes, affected users, direct links, and quotes.
4. 4.Rank items from most disruptive to minor into a dated table.
5. 5.Write a two-line action summary advising operator next steps.
6. 6.Save lessons to memory and refine rules for tricky page layouts.

Rules it follows

• •Never invent changes, version numbers, quotes, or direct links.
• •If the page cannot be read or has no release notes, state that clearly and stop.
• •Every row must include a verbatim quote and working link directly from the page.
• •Mark changes as breaking only when explicitly supported by the text.
• •Fresh retrieved page content always overrides remembered release facts.
• •Use memory as a guide, never as proof; fresh retrieved facts beat remembered facts.