create-forge 0.2.1__tar.gz → 0.3.1__tar.gz

{create_forge-0.2.1 → create_forge-0.3.1}/CHANGELOG.md

@@ -1,6 +1,52 @@
 # Changelog
 
 Generated by git-cliff from Conventional Commits.
+## [0.3.1] - 2026-09-08
+
+### Bug Fixes
+
+- Prevent template source credentials from reaching CLI output (#144)
+- Raise the Copier floor past the destination-escape advisories
+
+### Documentation
+
+- Publish 0.3.0 and close the Data Science roadmap (#130)
+- Add shared Forge user guide and simplify README (#131)
+## [0.3.0] - 2026-09-05
+
+### Bug Fixes
+
+- Handle template clone failures
+
+### Documentation
+
+- Link canonical organisation policy model
+- Sync canonical Stage 09 contracts
+- Validate the reference-client boundary
+- Add Data Science CLI roadmap
+- Add Data Science CLI issue plan
+- Link canonical Data Science project shape
+- Link canonical Data Science capability contracts
+- Link production Jupyter capability
+- Link production Scientific Python capability
+- Record forge-template 0.4.0 release
+- Define generic component-selection CLI conventions (#122)
+
+### Features
+
+- Define the downstream policy-consumption hook (#97)
+- Add a downstream CLI integration reference (#98)
+- Add dry-run support to update
+- Prompt engine options from discovery, not the registry (#102)
+- Adopt the forge-template 0.4 compatibility line (#121)
+- Select capabilities and platforms from discovery (#123)
+- Collect options for every selected component (#124)
+
+### Testing
+
+- Validate the Data Science preview pipeline (#125)
+- Validate installed Data Science generation (#127)
+- Complete the rollout regression and failure matrix (#128)
 ## [0.2.1] - 2026-08-31
 
 ### Bug Fixes

create_forge-0.3.1/PKG-INFO

@@ -0,0 +1,213 @@
+Metadata-Version: 2.5
+Name: create-forge
+Version: 0.3.1
+Summary: Scaffold modern Python projects from maintained templates.
+Project-URL: Homepage, https://github.com/Sandsy09/create-forge
+Project-URL: Repository, https://github.com/Sandsy09/create-forge
+Project-URL: Issues, https://github.com/Sandsy09/create-forge/issues
+Project-URL: Changelog, https://github.com/Sandsy09/create-forge/blob/main/CHANGELOG.md
+Author: Alex
+License-Expression: MIT
+License-File: LICENSE
+Keywords: cookiecutter,copier,project,scaffold,template
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: copier<10,>=9.15.2
+Requires-Dist: pydantic>=2.10
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: questionary>=2.0
+Requires-Dist: rich>=13.9
+Requires-Dist: typer>=0.16
+Provides-Extra: engine
+Requires-Dist: forge-template<0.5,>=0.4.1; extra == 'engine'
+Requires-Dist: uv<0.13,>=0.12; extra == 'engine'
+Description-Content-Type: text/markdown
+
+# create-forge
+
+[![CI](https://github.com/Sandsy09/create-forge/actions/workflows/ci.yml/badge.svg)](https://github.com/Sandsy09/create-forge/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/create-forge)](https://pypi.org/project/create-forge/)
+
+Create Python projects with packaging, quality checks, and a useful starting
+structure already in place.
+
+```bash
+uvx create-forge new
+```
+
+Requires [uv](https://docs.astral.sh/uv/getting-started/installation/), Git,
+and Python 3.11+ (uv can install Python for you). Configure your Git author
+name and email before generating a default Library project: generation
+creates local commits.
+
+**[Read the Forge user guide](https://sandsy09.github.io/create-forge/)**
+for walkthroughs, template choices, and troubleshooting.
+
+## How the repositories fit together
+
+| Repository | What it provides |
+| --- | --- |
+| **create-forge** | The CLI: prompts, project creation, updates, and diagnostics. |
+| [forge-template](https://github.com/Sandsy09/forge-template) | The project templates and composition engine used to generate files. |
+
+You normally use the CLI without cloning either repository. Generated
+projects do not depend on either Forge package at runtime.
+
+## Create your first project
+
+```bash
+uvx create-forge new "My Library"
+cd my-library
+uv run poe check
+```
+
+The default workflow creates an installable Library with a `src/` layout,
+uv, Ruff, pytest with coverage, mypy and/or pyright, pre-commit hooks, and
+GitHub Actions CI. Choose your build backend, versioning, license, and
+dependency-update tooling. MkDocs documentation is optional.
+
+The template is rendered by [Copier](https://copier.readthedocs.io/), which
+also supports bringing later template improvements into existing projects.
+
+## Install and manage the tool
+
+Use `uvx` for occasional runs, or install a persistent command:
+
+```bash
+uv tool install create-forge
+create-forge new
+uv tool upgrade create-forge
+```
+
+If the command is not on your PATH, run `uv tool update-shell` and restart
+your terminal.
+
+### Choose a CLI version
+
+```bash
+uvx create-forge@latest new
+uvx create-forge@0.3.0 new
+uv tool install "create-forge==0.3.0"
+```
+
+Plain `uvx create-forge` can reuse a cached or persistently installed
+version; `@latest` explicitly requests the latest release. Tool upgrades
+respect the constraints used at installation, so an exact pin stays pinned.
+To return to the latest release, run `uv tool install create-forge@latest`.
+See [installation and versions](https://sandsy09.github.io/create-forge/installation/).
+
+## Everyday usage
+
+| Command | Purpose |
+| --- | --- |
+| `uvx create-forge new` | Create a project interactively. |
+| `uvx create-forge list` | List the bundled Copier templates. |
+| `uvx create-forge update` | Update a Copier-generated project from its directory. |
+| `uvx create-forge doctor` | Diagnose Python, Git, uv, and package compatibility. |
+| `uvx create-forge config init` | Create an optional configuration file. |
+| `uvx create-forge config show` | Show resolved configuration and its sources. |
+
+For scripts and CI, provide a project name and skip questions with `--yes`:
+
+```bash
+uvx create-forge new "My Library" --yes --data github_org=your-org --data build_backend=hatchling --data versioning=vcs
+```
+
+Use `--path` to choose the destination and repeat `--data key=value` to
+preset answers. Run `uvx create-forge new --help` for the default workflow's
+options. Saved author details, GitHub organisation, and preferred template
+are covered in the [CLI guide](https://sandsy09.github.io/create-forge/cli/).
+
+### Choose a template version or source
+
+```bash
+uvx create-forge new "My Library" --template library --ref v0.4.1
+uvx create-forge new "Custom Project" --template-url https://github.com/you/your-template
+```
+
+`--ref` selects a Git revision in the **template repository**. It does not
+select the CLI version. Without it, Copier uses the latest suitable release
+tag. The bundled registry currently offers Library; upgrade the CLI to
+receive registry changes.
+
+Templates can execute code through generation and update tasks. Use custom
+sources only when you trust their content; `--yes` also skips the custom
+template confirmation.
+
+### Update a generated project
+
+From a clean, committed Copier-generated project:
+
+```bash
+uvx create-forge update --dry-run
+uvx create-forge update
+uv run poe check
+```
+
+Keep `.copier-answers.yml` committed. Review the resulting diff and resolve
+conflicts before committing. A dry run validates the update without applying
+it; it does not produce a file-by-file diff. Use `update --ref v0.4.1` to
+target a particular template version.
+
+## Preview: more project types and capabilities
+
+The `0.3.0` CLI also provides an opt-in engine preview using
+`forge-template>=0.4.1,<0.5`. These options are currently hidden from help.
+
+| Project type | Use it for |
+| --- | --- |
+| Library | A distributable Python package with a choice of packaging modes. |
+| CLI Application | A Typer application with a console command and tests. |
+| Data Science | A Python package with a starter notebook and Jupyter tooling. |
+
+Add **Jupyter** for notebook development or **Scientific Python** for NumPy,
+pandas, Matplotlib, and scikit-learn. Data Science requires Jupyter;
+Scientific Python is optional. These capabilities can also accompany the
+other preview archetypes.
+
+```bash
+uvx --from "create-forge[engine]==0.3.0" create-forge new "My Analysis" --engine-preview --archetype data-science --capability jupyter --yes --data license=mit
+cd my-analysis
+uv run --locked poe check
+uv run poe notebook
+```
+
+For regular preview use, install with `uv tool install "create-forge[engine]"`.
+The [project guide](https://sandsy09.github.io/create-forge/projects/) explains
+each type's output and links to complete recipes.
+
+**Preview projects do not support `create-forge update`.** Their shared
+tooling differs from the default Copier template; the preview does not
+generate its CI workflows or install Git hooks. `--template`,
+`--template-url`, and `--ref` apply only to the Copier workflow.
+
+## What's next
+
+The Foundation and Data Science roadmaps are complete. Making the engine
+the default generation workflow is a planned direction with no scheduled
+release. Follow [open work](https://github.com/Sandsy09/create-forge/issues)
+and [releases](https://github.com/Sandsy09/create-forge/releases) for updates,
+or suggest a project type, capability, or guide you would find useful.
+
+## Feedback and contributing
+
+- [Report a CLI problem or suggest a feature](https://github.com/Sandsy09/create-forge/issues/new/choose).
+- [Request or correct documentation](https://github.com/Sandsy09/create-forge/issues/new?template=documentation.yml).
+- [Report generated-content or capability problems](https://github.com/Sandsy09/forge-template/issues/new/choose).
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development and PR checks, and
+the [reference index](https://sandsy09.github.io/create-forge/reference/) for
+engine APIs and architecture documents. Report vulnerabilities through
+[SECURITY.md](SECURITY.md).
+
+## License
+
+MIT — see [LICENSE](LICENSE).

create_forge-0.3.1/README.md

@@ -0,0 +1,180 @@
+# create-forge
+
+[![CI](https://github.com/Sandsy09/create-forge/actions/workflows/ci.yml/badge.svg)](https://github.com/Sandsy09/create-forge/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/create-forge)](https://pypi.org/project/create-forge/)
+
+Create Python projects with packaging, quality checks, and a useful starting
+structure already in place.
+
+```bash
+uvx create-forge new
+```
+
+Requires [uv](https://docs.astral.sh/uv/getting-started/installation/), Git,
+and Python 3.11+ (uv can install Python for you). Configure your Git author
+name and email before generating a default Library project: generation
+creates local commits.
+
+**[Read the Forge user guide](https://sandsy09.github.io/create-forge/)**
+for walkthroughs, template choices, and troubleshooting.
+
+## How the repositories fit together
+
+| Repository | What it provides |
+| --- | --- |
+| **create-forge** | The CLI: prompts, project creation, updates, and diagnostics. |
+| [forge-template](https://github.com/Sandsy09/forge-template) | The project templates and composition engine used to generate files. |
+
+You normally use the CLI without cloning either repository. Generated
+projects do not depend on either Forge package at runtime.
+
+## Create your first project
+
+```bash
+uvx create-forge new "My Library"
+cd my-library
+uv run poe check
+```
+
+The default workflow creates an installable Library with a `src/` layout,
+uv, Ruff, pytest with coverage, mypy and/or pyright, pre-commit hooks, and
+GitHub Actions CI. Choose your build backend, versioning, license, and
+dependency-update tooling. MkDocs documentation is optional.
+
+The template is rendered by [Copier](https://copier.readthedocs.io/), which
+also supports bringing later template improvements into existing projects.
+
+## Install and manage the tool
+
+Use `uvx` for occasional runs, or install a persistent command:
+
+```bash
+uv tool install create-forge
+create-forge new
+uv tool upgrade create-forge
+```
+
+If the command is not on your PATH, run `uv tool update-shell` and restart
+your terminal.
+
+### Choose a CLI version
+
+```bash
+uvx create-forge@latest new
+uvx create-forge@0.3.0 new
+uv tool install "create-forge==0.3.0"
+```
+
+Plain `uvx create-forge` can reuse a cached or persistently installed
+version; `@latest` explicitly requests the latest release. Tool upgrades
+respect the constraints used at installation, so an exact pin stays pinned.
+To return to the latest release, run `uv tool install create-forge@latest`.
+See [installation and versions](https://sandsy09.github.io/create-forge/installation/).
+
+## Everyday usage
+
+| Command | Purpose |
+| --- | --- |
+| `uvx create-forge new` | Create a project interactively. |
+| `uvx create-forge list` | List the bundled Copier templates. |
+| `uvx create-forge update` | Update a Copier-generated project from its directory. |
+| `uvx create-forge doctor` | Diagnose Python, Git, uv, and package compatibility. |
+| `uvx create-forge config init` | Create an optional configuration file. |
+| `uvx create-forge config show` | Show resolved configuration and its sources. |
+
+For scripts and CI, provide a project name and skip questions with `--yes`:
+
+```bash
+uvx create-forge new "My Library" --yes --data github_org=your-org --data build_backend=hatchling --data versioning=vcs
+```
+
+Use `--path` to choose the destination and repeat `--data key=value` to
+preset answers. Run `uvx create-forge new --help` for the default workflow's
+options. Saved author details, GitHub organisation, and preferred template
+are covered in the [CLI guide](https://sandsy09.github.io/create-forge/cli/).
+
+### Choose a template version or source
+
+```bash
+uvx create-forge new "My Library" --template library --ref v0.4.1
+uvx create-forge new "Custom Project" --template-url https://github.com/you/your-template
+```
+
+`--ref` selects a Git revision in the **template repository**. It does not
+select the CLI version. Without it, Copier uses the latest suitable release
+tag. The bundled registry currently offers Library; upgrade the CLI to
+receive registry changes.
+
+Templates can execute code through generation and update tasks. Use custom
+sources only when you trust their content; `--yes` also skips the custom
+template confirmation.
+
+### Update a generated project
+
+From a clean, committed Copier-generated project:
+
+```bash
+uvx create-forge update --dry-run
+uvx create-forge update
+uv run poe check
+```
+
+Keep `.copier-answers.yml` committed. Review the resulting diff and resolve
+conflicts before committing. A dry run validates the update without applying
+it; it does not produce a file-by-file diff. Use `update --ref v0.4.1` to
+target a particular template version.
+
+## Preview: more project types and capabilities
+
+The `0.3.0` CLI also provides an opt-in engine preview using
+`forge-template>=0.4.1,<0.5`. These options are currently hidden from help.
+
+| Project type | Use it for |
+| --- | --- |
+| Library | A distributable Python package with a choice of packaging modes. |
+| CLI Application | A Typer application with a console command and tests. |
+| Data Science | A Python package with a starter notebook and Jupyter tooling. |
+
+Add **Jupyter** for notebook development or **Scientific Python** for NumPy,
+pandas, Matplotlib, and scikit-learn. Data Science requires Jupyter;
+Scientific Python is optional. These capabilities can also accompany the
+other preview archetypes.
+
+```bash
+uvx --from "create-forge[engine]==0.3.0" create-forge new "My Analysis" --engine-preview --archetype data-science --capability jupyter --yes --data license=mit
+cd my-analysis
+uv run --locked poe check
+uv run poe notebook
+```
+
+For regular preview use, install with `uv tool install "create-forge[engine]"`.
+The [project guide](https://sandsy09.github.io/create-forge/projects/) explains
+each type's output and links to complete recipes.
+
+**Preview projects do not support `create-forge update`.** Their shared
+tooling differs from the default Copier template; the preview does not
+generate its CI workflows or install Git hooks. `--template`,
+`--template-url`, and `--ref` apply only to the Copier workflow.
+
+## What's next
+
+The Foundation and Data Science roadmaps are complete. Making the engine
+the default generation workflow is a planned direction with no scheduled
+release. Follow [open work](https://github.com/Sandsy09/create-forge/issues)
+and [releases](https://github.com/Sandsy09/create-forge/releases) for updates,
+or suggest a project type, capability, or guide you would find useful.
+
+## Feedback and contributing
+
+- [Report a CLI problem or suggest a feature](https://github.com/Sandsy09/create-forge/issues/new/choose).
+- [Request or correct documentation](https://github.com/Sandsy09/create-forge/issues/new?template=documentation.yml).
+- [Report generated-content or capability problems](https://github.com/Sandsy09/forge-template/issues/new/choose).
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development and PR checks, and
+the [reference index](https://sandsy09.github.io/create-forge/reference/) for
+engine APIs and architecture documents. Report vulnerabilities through
+[SECURITY.md](SECURITY.md).
+
+## License
+
+MIT — see [LICENSE](LICENSE).

{create_forge-0.2.1 → create_forge-0.3.1}/docs/adr/README.md

@@ -24,6 +24,23 @@ format](https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions
 - [0019 — CLI archetype-parity review](0019-cli-archetype-parity-review.md)
 - [0020 — Test the public engine path end to end](0020-engine-path-end-to-end-tests.md)
 - [0021 — Finalise engine-generated lockfiles in the client](0021-client-finalises-engine-lockfiles.md)
+- [0022 — Downstream organisation-policy consumption hook](0022-downstream-organisation-policy-hook.md)
+- [0023 — Downstream client reference](0023-downstream-client-reference.md)
+- [0024 — Keep create-forge a reference client, not a framework dependency](0024-reference-client-not-framework-dependency.md)
+- [0025 — Prompt the engine path from discovery, not the Copier registry](0025-engine-native-prompt-flow.md)
+- [0026 — Adopt the forge-template 0.4 compatibility line](0026-adopt-the-0-4-engine-compatibility-line.md)
+- [0027 — Select components from discovery, with owner-qualified options](0027-generic-component-selection-conventions.md)
+- [0028 — Select capabilities and platforms from one discovered catalogue](0028-discovery-driven-component-selection.md)
+- [0029 — Collect and serialise options for every selected component](0029-per-component-option-collection.md)
+- [0030 — Validate the Data Science preview pipeline against the released engine](0030-data-science-preview-pipeline-validation.md)
+- [0031 — Adopt the reviewed forge-template 0.4.1 release](0031-adopt-the-reviewed-forge-template-0-4-1-release.md)
+- [0032 — Validate Data Science through the installed create-forge candidate](0032-validate-installed-data-science-generation.md)
+- [0033 — Complete the rollout regression and failure matrix at the installed boundary](0033-complete-rollout-regression-validation.md)
+- [0034 — Publish create-forge 0.3.0 and close the Data Science roadmap](0034-publish-0-3-0-and-close-roadmap-v2.md)
+- [0035 — Shared Forge user documentation](0035-shared-forge-user-documentation.md)
+- [0036 — Keep credentials out of template sources and CLI diagnostics](0036-template-source-credentials.md)
+- [0037 — Pin external Actions to reviewed commits and scope permissions per job](0037-immutable-workflow-actions.md)
+- [0038 — Raise the Copier floor past the destination-escape advisories and hold uv](0038-dependency-floor-review.md)
 
 Add a new record by copying the most recent one and incrementing the number.
 Records are immutable: supersede them rather than editing.

{create_forge-0.2.1 → create_forge-0.3.1}/docs/roadmap-v1/README.md

@@ -1,5 +1,9 @@
 # Forge Foundation Roadmap Pack — Two-Repository Edition
 
+> **Completed historical roadmap.** Stages 00–09 are closed. Paths remain
+> stable as decision and issue evidence. New Data Science work continues in
+> the [Stage 10–14 roadmap](../roadmap-v2/README.md).
+
 This revision models Forge as two independent repositories that work together through an explicit contract:
 
 - **`forge-template`** owns generated content, component metadata and the template/composition engine.
@@ -51,8 +55,23 @@ workflows, which remain independently owned and unchanged.
 The canonical
 [ProjectSpec protocol v1](https://github.com/Sandsy09/forge-template/blob/main/docs/project-spec.md)
 defines the strict effective generation request owned by `forge-template`.
-`create-forge` retains construction and user-facing orchestration, which remain
-unimplemented until the supported engine cutover.
+`create-forge` retains construction and user-facing orchestration. The canonical
+[organisation-policy protocol v1](https://github.com/Sandsy09/forge-template/blob/main/docs/organisation-policy.md)
+defines how downstream clients resolve component-selection policy before
+constructing that effective request. CF-09.01
+([ADR 0022](https://github.com/Sandsy09/create-forge/blob/main/docs/adr/0022-downstream-organisation-policy-hook.md))
+delivered the client hook; `create-forge` still consumes no policy itself.
+Forge-template Epic 09 is complete through its canonical
+[extension contract](https://github.com/Sandsy09/forge-template/blob/main/docs/extension-points.md),
+[policy fixture](https://github.com/Sandsy09/forge-template/blob/main/docs/organisation-policy-fixtures.md),
+[compatibility policy](https://github.com/Sandsy09/forge-template/blob/main/docs/compatibility-policy.md),
+and [no-copy proof](https://github.com/Sandsy09/forge-template/blob/main/docs/no-copy-inheritance.md).
+Forge-template [ADRs 0039–0042](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/README.md)
+record those four decisions.
+Create-forge Epic #40 and #53–#55 are complete under
+[ADR 0024](../adr/0024-reference-client-not-framework-dependency.md), which
+validates the client-owned half without making `create-forge` a shared
+framework dependency.
 The canonical
 [component manifest protocol v1](https://github.com/Sandsy09/forge-template/blob/main/docs/component-manifests.md)
 defines engine-owned bundled component metadata and compatibility. The

{create_forge-0.2.1 → create_forge-0.3.1}/docs/roadmap-v1/roadmap/08-reference-archetype-validation/README.md

@@ -44,7 +44,11 @@
   (`pipeline._resolved_component_options`) is now gated by a discovered
   descriptor rather than a hardcoded archetype id. The engine path's
   Library-shaped prompt set was recorded, not fixed, and tracked by
-  [create-forge#91](https://github.com/Sandsy09/create-forge/issues/91).
+  [create-forge#91](https://github.com/Sandsy09/create-forge/issues/91) —
+  since closed via
+  [ADR 0025](https://github.com/Sandsy09/create-forge/blob/main/docs/adr/0025-engine-native-prompt-flow.md):
+  `--engine-preview` now prompts directly from the selected archetype's own
+  discovered `ComponentDescriptor.options` and reads no registry data at all.
 - ~~**CF-08.04 — Extend end-to-end generation to the public engine**~~ —
   complete via
   [ADR 0020](https://github.com/Sandsy09/create-forge/blob/main/docs/adr/0020-engine-path-end-to-end-tests.md)

create_forge-0.3.1/docs/roadmap-v1/roadmap/09-blueprint-compatibility/README.md

@@ -0,0 +1,62 @@
+# Stage 09 — Blueprint Compatibility
+
+## Repository ownership
+
+### forge-template
+
+- [x] **FT-09.01 — Define organisation policy model** — completed by the
+  canonical [organisation-policy protocol v1](https://github.com/Sandsy09/forge-template/blob/main/docs/organisation-policy.md),
+  [ADR 0038](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0038-organisation-policy-selection-model.md),
+  and [forge-template PR #89](https://github.com/Sandsy09/forge-template/pull/89).
+- [x] **FT-09.02 — Define safe override and extension points** — completed by
+  the canonical [extension contract](https://github.com/Sandsy09/forge-template/blob/main/docs/extension-points.md),
+  [ADR 0039](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0039-deny-policy-file-overrides.md),
+  and [forge-template PR #90](https://github.com/Sandsy09/forge-template/pull/90).
+- [x] **FT-09.03 — Create generic downstream policy reference fixture** —
+  completed by the canonical [fixture guide](https://github.com/Sandsy09/forge-template/blob/main/docs/organisation-policy-fixtures.md),
+  [ADR 0040](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0040-organisation-policy-reference-fixture.md),
+  and [forge-template PR #91](https://github.com/Sandsy09/forge-template/pull/91).
+- [x] **FT-09.04 — Define Forge-Blueprint compatibility policy** — completed
+  by the canonical [compatibility policy](https://github.com/Sandsy09/forge-template/blob/main/docs/compatibility-policy.md),
+  [ADR 0041](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0041-forge-blueprint-compatibility-policy.md),
+  and [forge-template PR #92](https://github.com/Sandsy09/forge-template/pull/92).
+- [x] **FT-09.05 — Validate no-copy inheritance model** — completed by the
+  canonical [no-copy proof](https://github.com/Sandsy09/forge-template/blob/main/docs/no-copy-inheritance.md),
+  [ADR 0042](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0042-validate-no-copy-downstream-inheritance.md),
+  and [forge-template PR #93](https://github.com/Sandsy09/forge-template/pull/93).
+
+Forge-template [Epic #18](https://github.com/Sandsy09/forge-template/issues/18)
+and its milestone are complete. Its contracts keep policy selection-only,
+deny arbitrary file replacement, define compatibility, and prove public-
+facade reuse without copied Foundation/component source. The private fixture
+catalogue remains a forge-template test seam, not a client plugin mechanism.
+
+### create-forge
+
+- Epic: [CF-EPIC-09 / #40](https://github.com/Sandsy09/create-forge/issues/40)
+- [x] [**CF-09.01 — Define downstream policy-consumption hook**](https://github.com/Sandsy09/create-forge/issues/53)
+  — complete. `pipeline.build_generation_request` accepts a `selection`/
+  `provenance` pair built from `spec.SelectionRequest`/`SelectionProvenance`;
+  `create-forge` ships no resolver and reads no policy document by design.
+  See [ADR 0022](https://github.com/Sandsy09/create-forge/blob/main/docs/adr/0022-downstream-organisation-policy-hook.md)
+  and the canonical [downstream policy-consumption contract](https://github.com/Sandsy09/create-forge/blob/main/docs/organisation-policy-consumption.md).
+- [x] [**CF-09.02 — Create downstream CLI integration reference**](https://github.com/Sandsy09/create-forge/issues/54)
+  — complete. `examples/downstream_cli.py`: a second, independent
+  Blueprint-style CLI over the public `forge_template` facade, with its own
+  compatibility bounds and its own minimal organisation-policy resolver, and
+  no dependency on `create-forge` at all (an AST guard proves it). See
+  [ADR 0023](https://github.com/Sandsy09/create-forge/blob/main/docs/adr/0023-downstream-client-reference.md)
+  and the canonical [downstream client reference](https://github.com/Sandsy09/create-forge/blob/main/docs/downstream-client-reference.md).
+- [x] [**CF-09.03 — Validate create-forge is a reference client, not a framework dependency**](https://github.com/Sandsy09/create-forge/issues/55)
+  — complete. [ADR 0024](../../../adr/0024-reference-client-not-framework-dependency.md)
+  records the strict one-way dependency, the living
+  [integration contract](../../../integration-contract.md) maps every
+  acceptance criterion to executable evidence, and both production
+  archetypes are checked for Forge-free generated dependencies and locks.
+
+## Stage completion rule
+
+- [x] Repo-local issues are complete or explicitly deferred.
+- [x] Cross-repository blockers are resolved.
+- [x] Public contracts changed by this stage are documented/versioned.
+- [x] No implementation concern is duplicated across repositories.

create_forge-0.3.1/docs/roadmap-v2/README.md

@@ -0,0 +1,57 @@
+# Forge Data Science Roadmap — Two-Repository Edition
+
+This roadmap continues the completed
+[Forge Foundation roadmap](../roadmap-v1/README.md) through Stages 10–14.
+It plans the next production archetype without reopening the Foundation,
+composition, reference-client, or Blueprint decisions completed in Stages
+00–09.
+
+The target is a package-backed, notebook-oriented Data Science project with
+reusable optional capabilities. Exact scientific libraries, notebook front
+ends, data-versioning systems, model tooling, and deployment integrations are
+not selected here; Stage 10 owns those decisions.
+
+Delivery remains behind `create-forge new --engine-preview`. Retiring the
+default direct-Copier path is a separate future initiative.
+
+Stages 10–12 are complete. The package-bound five-component catalogue is
+published as
+[`forge-template 0.4.0`](https://github.com/Sandsy09/forge-template/releases/tag/v0.4.0)
+on [PyPI](https://pypi.org/project/forge-template/0.4.0/). Stage 13 is
+complete: CF-13.01 (ADR 0026) adopted the `forge-template>=0.4,<0.5`
+compatibility line, so `--engine-preview` discovery now returns all five
+descriptors, and CF-13.02 (ADR 0027) fixed the generic component-selection
+CLI conventions, which CF-13.03 (ADR 0028) implemented for capabilities and
+platforms and CF-13.04 (ADR 0029) for per-component options, and CF-13.05
+(ADR 0030) validated the Data Science composition through the shared pipeline
+against the released engine, closing CF-EPIC-13. Stage 14 takes the released
+client and engine pair through installed-console validation and rollout.
+Provider Stage 14 is complete and published the reviewed
+`forge-template 0.4.1` release. CF-14.01 (ADR 0031) adopts it as create-forge's
+`>=0.4.1,<0.5` lower bound and prepares create-forge `0.3.0`; CF-14.02
+(ADR 0032) completes installed-console Data Science validation, and CF-14.03
+(ADR 0033) completes the installed regression and failure matrix. CF-14.04
+(ADR 0034) published create-forge `0.3.0` to PyPI, verified the released pair,
+and closed CF-EPIC-14 and both Stage 13 and Stage 14 milestones. **The Data
+Science roadmap is complete in both repositories.**
+
+## Repository roles
+
+- **forge-template** owns the Data Science contract, capabilities, archetype,
+  composition review, generated content, and engine releases.
+- **create-forge** owns discovery-driven user input, ProjectSpec construction,
+  diagnostics, staging, lock finalisation, and end-to-end client validation.
+
+See the [architecture](ARCHITECTURE.md),
+[ownership model](REPOSITORY-OWNERSHIP.md), and
+[stage roadmap](ROADMAP.md) for the complete boundary.
+
+## Live GitHub work
+
+Six epics and 24 child issues are filed across the two repositories. GitHub
+issue bodies and native parent/dependency relationships are authoritative:
+
+- [forge-template epic index](https://github.com/Sandsy09/forge-template/blob/main/docs/roadmap-v2/github-issues/forge-template/ISSUE-INDEX.md)
+- [create-forge epic index](https://github.com/Sandsy09/create-forge/blob/main/docs/roadmap-v2/github-issues/create-forge/ISSUE-INDEX.md)
+- [cross-repository dependency matrix](github-issues/CROSS-REPO-DEPENDENCIES.md)
+- [GitHub setup and taxonomy](github-issues/GITHUB-SETUP.md)