Because it ends at the click. It tells you a page earned four thousand impressions and eleven clicks and nothing about what those eleven people did next, so the value of fixing it is unknowable there.
Search Console performance data lands on each URL's own record, alongside everything else known about that page.
Queries, impressions, clicks, position and CTR attach to the page record. Because that record also carries sessions, enquiries and deals, one view spans query to revenue.
A page at position six with four thousand impressions and a 0.3% click rate is visibly a title and description problem, and both are on the same screen as the number.
It will not show anonymised queries. Search Console withholds a portion, and Growth leaves the gap visible rather than estimating into it.
GA4 sessions, the cluster the page is meant to answer, its last edit date, and any enquiry it produced in Flow.
From connection onward, plus whatever the API returns at setup.
Yes, separated by search type.
Yes, with the page's own edit history on the same timeline.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.