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

[fas89]

cli-version.json pinned 0.15.0, so cli-consistency.yml was installing and validating against a superseded release while readers got 0.15.1.

0.15.1 is a front-door patch with no behaviour change, so no page needed rewriting — only the pointers moved.

What the sweep got right

It flagged 16 current-pointer claims — release bullets, pip install data-product-forge== specs, "this docs set tracks" — and left every "as of 0.15.0 the engine enforces" statement alone.

That distinction matters. Those "since" statements remain true, and a sweep that bumped them would turn every patch release into a wave of quiet falsehoods.

The last one was the root README

Caught by the same widening added two days ago precisely because that file sat outside every gate. My own fix list here was filtered to docs/ paths and missed it again — and the gate caught it.

That is the first time in this work a gate caught something I had missed, rather than the other way round.

Verification

Against the real published 0.15.1 wheel, not the working tree:

OK: fluid CLI version matches docs (0.15.1)
OK: all 69 CLI subcommands are documented (84 pages, subdirectories included)
OK: `fluid init --quickstart` emits fluidVersion 0.7.2 (matches pin)
OK: contract pins agree with the CLI's bundled schemas
OK: all 1093 documented `fluid` invocations match the pinned CLI
OK: every version claim in docs/ agrees with the pin

Site builds, 213 pages.