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

README.md

@@ -15,7 +15,7 @@ Fluid Forge is a contract-first CLI for building, validating, and deploying data
 
 ## Current Versioning
 
-- Current CLI release documented here: `0.15.0`
+- Current CLI release documented here: `0.15.1`
 - Current scaffolded contract schema examples: `fluidVersion: 0.7.5`
 
 Those are different on purpose. `fluid version` reports the installed CLI release, while `fluidVersion` inside a contract selects the contract schema version.

docs/.vuepress/cli-version.json

@@ -1,6 +1,6 @@
 {
-  "supportedCliVersion": "0.15.0",
-  "supportedCliInstallSpec": "data-product-forge==0.15.0",
+  "supportedCliVersion": "0.15.1",
+  "supportedCliInstallSpec": "data-product-forge==0.15.1",
   "supportedFluidContractVersion": "0.7.5",
   "quickstartScaffoldVersion": "0.7.2",
   "supportedSdkVersion": "0.10.0",

docs/README.md

@@ -80,7 +80,7 @@ fluid apply contract.fluid.yaml --yes
 
 This docs site currently tracks:
 
-- CLI release `0.15.0`
+- CLI release `0.15.1`
 - Contract schema `0.7.5` as the stable default, with `0.7.6` open as an opt-in preview
 
 Which `fluidVersion` a fresh scaffold actually writes depends on which scaffold path you took, and the quickstart is not the same as the factory. The rule, with the per-path numbers, lives in one place: [Understand the version numbers](/forge_docs/getting-started/#understand-the-version-numbers). Run `fluid version` for the authoritative list of accepted schema versions on the CLI you have installed.

docs/cli/README.md

@@ -8,7 +8,7 @@ The page you actually want is [**CLI by task →**](./tasks/) — narrative walk
 
 ## Read this first
 
-- CLI release examples in this section use `0.15.0`
+- CLI release examples in this section use `0.15.1`
 - Contract examples use `fluidVersion: 0.7.2`
 - `fluid version` and `fluidVersion` are different things
 - The pinned CLI version is recorded in [`docs/.vuepress/cli-version.json`](https://github.com/Agenticstiger/forge_docs/blob/main/docs/.vuepress/cli-version.json) and enforced by the [`cli-consistency`](https://github.com/Agenticstiger/forge_docs/actions/workflows/cli-consistency.yml) workflow.

docs/cli/mission.md

@@ -222,7 +222,7 @@ cosmetics ([`0.13.0` security fixes](../RELEASE_NOTES_0.13.0.md#security)).
 ```yaml
 - name: Mission gate
   run: |
-    pip install data-product-forge==0.15.0
+    pip install data-product-forge==0.15.1
     fluid mission check quality-coverage contract.fluid.yaml
 ```
 

docs/getting-started/README.md

@@ -38,7 +38,7 @@ The current docs baseline is `0.15.0` — the stable tag was cut on `2026-09-14`
 
 ```bash
 pip install --upgrade data-product-forge
-pip install "data-product-forge==0.15.0"    # exact pin
+pip install "data-product-forge==0.15.1"    # exact pin
 ```
 
 Pre-releases (when published) ship to PyPI as PEP 440 pre-releases — `pip install` skips them by default. The `--pre` flag opts in.
@@ -58,7 +58,7 @@ fluid version
 fluid doctor
 ```
 
-This docs set tracks CLI release `0.15.0`. Docs updates land in lockstep with each release; if you're on an older CLI, some `--mode` / `--target` flags mentioned here won't be present yet — see the [CLI index](../cli/README.md) for what maps to what.
+This docs set tracks CLI release `0.15.1`. Docs updates land in lockstep with each release; if you're on an older CLI, some `--mode` / `--target` flags mentioned here won't be present yet — see the [CLI index](../cli/README.md) for what maps to what.
 
 > **Extending the CLI?** Fluid Forge ships three plugin extension points and a companion SDK on PyPI. If your team has its own CI templates, scaffolding standards, or governance rules, see **[SDK & Plugins](../sdk-and-plugins/)**.
 

docs/providers/README.md

@@ -8,7 +8,7 @@ Fluid Forge uses one contract format across local and provider-backed execution
 
 ## Docs baseline
 
-- CLI release covered by the primary docs: `0.15.0`
+- CLI release covered by the primary docs: `0.15.1`
 - Default scaffold (`fluid init --quickstart`) emits `fluidVersion: 0.7.2`
 - Discovery-based scaffolds (`fluid init --discover`, `fluid forge`, `fluid product-new`) emit `fluidVersion: 0.7.5` — the latest bundled schema
 

docs/providers/aws.md

@@ -3,7 +3,7 @@
 Deploy data products to Amazon Web Services — S3, Glue, Athena — using the same contract and CLI commands as every other provider.
 
 **Status:** ✅ Production  
-**Docs Baseline:** CLI `0.15.0`<br>
+**Docs Baseline:** CLI `0.15.1`<br>
 **Tested Services:** S3, Glue Data Catalog, Athena, IAM
 
 > **Why it matters**

docs/providers/gcp.md

@@ -1,7 +1,7 @@
 # GCP Provider
 
 **Status:** ✅ Production Ready  
-**Docs Baseline:** CLI `0.15.0`<br>
+**Docs Baseline:** CLI `0.15.1`<br>
 **Services:** BigQuery, Cloud Storage, IAM, Cloud Run, Pub/Sub
 
 > **Why it matters**

docs/providers/local.md

@@ -1,7 +1,7 @@
 # Local Provider
 
 **Status:** ✅ Production Ready  
-**Docs Baseline:** CLI `0.15.0`<br>
+**Docs Baseline:** CLI `0.15.1`<br>
 **Database:** DuckDB, SQLite
 
 > **Why it matters**

docs/providers/snowflake.md

@@ -3,7 +3,7 @@
 Deploy data products to Snowflake Data Cloud — databases, schemas, tables, RBAC grants — using the same contract and CLI commands as every other provider.
 
 **Status:** ✅ Production  
-**Docs Baseline:** CLI `0.15.0`<br>
+**Docs Baseline:** CLI `0.15.1`<br>
 **Tested Services:** Databases, Schemas, Tables, Warehouses, RBAC Grants
 
 > **Why it matters**

docs/sdk-and-plugins/reference/companion-packages.md

@@ -48,7 +48,7 @@ The PyPI name reflects the product brand (`data-product-forge`). The import path
 
 ```toml
 dependencies = [
-    "data-product-forge==0.15.0",  # pin exact for reproducibility
+    "data-product-forge==0.15.1",  # pin exact for reproducibility
 ]
 ```
 

docs/sdk-and-plugins/reference/trust-model.md

@@ -167,7 +167,7 @@ Plugins are tested, scanned, and approved by your platform team before showing u
 
 ```toml
 # In your deploy environment's pyproject.toml or requirements:
-data-product-forge==0.15.0
+data-product-forge==0.15.1
 data-product-forge-sdk==0.10.0
 data-product-forge-custom-scaffold==0.4.1
 my-org-validators==1.2.0

docs/vision.md

@@ -147,7 +147,7 @@ fluid market --search "customer analytics"
 
 ## Versioning in the docs
 
-- Current CLI release baseline: `0.15.0`
+- Current CLI release baseline: `0.15.1`
 - Current scaffolded contract examples: `fluidVersion: 0.7.5`
 
 That split is intentional. The CLI release and the contract schema version move on related but different timelines.

docs/walkthrough/export-orchestration.md

@@ -1,6 +1,6 @@
 # Generating Orchestration Code from Contracts
 
-**Docs Baseline:** CLI `0.15.0`<br>
+**Docs Baseline:** CLI `0.15.1`<br>
 **Status:** ✅ Production Ready
 
 ::: warning Compatibility note

docs/walkthrough/universal-pipeline.md

@@ -7,7 +7,7 @@ One Jenkinsfile. Every provider. Zero if/then logic.
 **Provider-specific logic:** None
 
 ::: warning Compatibility note
-This walkthrough includes some older `0.7.1` contract-era examples. The primary docs baseline now tracks CLI `0.15.0`, current scaffolded contracts use `fluidVersion: 0.7.5`, and orchestration docs prefer `fluid generate schedule --scheduler airflow`.
+This walkthrough includes some older `0.7.1` contract-era examples. The primary docs baseline now tracks CLI `0.15.1`, current scaffolded contracts use `fluidVersion: 0.7.5`, and orchestration docs prefer `fluid generate schedule --scheduler airflow`.
 :::
 
 ---