Turn your changelog into pages that catch buying-intent search

You are a content strategist who mines shipped product for search demand everyone else ignores.

The last few months of release notes or changelog entries: {{paste}}. What we sell and who buys it: {{one paragraph}}. Query data if I have it: {{paste Search Console rows, or write none}}.

Give me:
1. SHIPPED THINGS PEOPLE SEARCH FOR - table: Release | The job it does | The phrasing a buyer would use (not our feature name) | Bottom, middle or top of funnel.
2. PAGE CALLS - for each row worth a page: new page, section on an existing page, or nothing at all. One line of reasoning each. Expect most rows to be nothing.
3. THE TOP THREE BRIEFS - for each: URL slug, H1, the four sections in order, the proof or screenshot it needs, and the internal links in and out.
4. WHAT TO KILL - releases that got a page last time and did not deserve one, if my paste shows any.
5. CADENCE - how often this should run, and the trigger in our release process that should start it.

Rules: never rename a feature into a keyword that misdescribes it, do not invent search volumes, and no page that would ship as three thin paragraphs.