docs: track 0.15.2, which is what pip install now gives you

[fas89]

data-product-forge v0.15.2 is on PyPI, so the docs pin follows it.

Ordering, which is not optional. cli-consistency.yml runs pip install data-product-forge==<pin> on every PR. Bumping the pin before the release is published fails that job on an install that cannot resolve — so: publish, verify, then pin.

The sweep found what a grep would not

Bumping cli-version.json alone turned check_cli_docs.py red, and it named every disagreeing line in turn:

file	line
README.md	repo-root "Current CLI release documented here"
docs/README.md	landing banner title, the pip install sentence, and the release-line bullet
docs/vision.md	"Current CLI release baseline"
docs/providers/{aws,gcp,local,snowflake}.md	Docs Baseline: banners
docs/walkthrough/{export-orchestration,universal-pipeline}.md	baseline banners
docs/{cli,providers}/README.md	index "release covered/examples use" lines
docs/getting-started/README.md	the exact pin and the tracking sentence
docs/cli/mission.md, docs/sdk-and-plugins/reference/{trust-model,companion-packages}.md	exact-pin examples

Fourteen files. That gate is the one I widened two sessions ago after it proved blind to the repo-root README — this run is it earning its keep.

Deliberately not changed

One 0.15.1 stays, on the landing page, where it names 0.15.1 and 0.15.2 as the two front-door patches with no release-notes page of their own. That is history, and history is not rewritten to match today.

Verified

check_cli_docs.py   OK: fluid CLI version matches docs (0.15.2)
                    OK: all 1093 documented `fluid` invocations match the pinned CLI
                    OK: every version claim in docs/ agrees with the pin (CLI 0.15.2)
npm run docs:build  exit 0, 213 pages
check-dist-links    Clean: 107,738 absolute references across 219 built pages
                    canaries: 5 resolved (3 exact, 1 index, 1 pretty), 1 missing-base, 2 missing-file