chore: update references to new git project name

Signed-off-by: Frederico Araujo <frederico.araujo@ibm.com>

Author: araujof

CHANGELOG.md

@@ -21,5 +21,5 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).
 
 - Initial release
 
-[Unreleased]: https://github.com/contextforge-org/contextforge-plugins-framework/compare/0.1.0...HEAD
-[0.1.0]: https://github.com/contextforge-org/contextforge-plugins-framework/releases/tag/0.1.0
+[Unreleased]: https://github.com/contextforge-org/cpex/compare/0.1.0...HEAD
+[0.1.0]: https://github.com/contextforge-org/cpex/releases/tag/0.1.0

CONTRIBUTING.md

@@ -5,10 +5,10 @@
 Our project welcomes external contributions. If you have an itch, please feel
 free to scratch it.
 
-To contribute code or documentation, please submit a [pull request](https://github.com/contextforge-org/contextforge-plugins-framework/pulls).
+To contribute code or documentation, please submit a [pull request](https://github.com/contextforge-org/cpex/pulls).
 
 A good way to familiarize yourself with the codebase and contribution process is
-to look for and tackle low-hanging fruit in the [issue tracker](https://github.com/contextforge-org/contextforge-plugins-framework/issues).
+to look for and tackle low-hanging fruit in the [issue tracker](https://github.com/contextforge-org/cpex/issues).
 Before embarking on a more ambitious contribution, please quickly [get in touch](#communication) with us.
 
 **Note: We appreciate your effort, and want to avoid a situation where a contribution
@@ -17,14 +17,14 @@ cannot be accepted at all!**
 
 ### Proposing new features
 
-If you would like to implement a new feature, please [raise an issue](https://github.com/contextforge-org/contextforge-plugins-framework/issues)
+If you would like to implement a new feature, please [raise an issue](https://github.com/contextforge-org/cpex/issues)
 before sending a pull request so the feature can be discussed. This is to avoid
 you wasting your valuable time working on a feature that the project developers
 are not interested in accepting into the code base.
 
 ### Fixing bugs
 
-If you would like to fix a bug, please [raise an issue](https://github.com/contextforge-org/contextforge-plugins-framework/issues) before sending a
+If you would like to fix a bug, please [raise an issue](https://github.com/contextforge-org/cpex/issues) before sending a
 pull request so it can be tracked.
 
 ### Merge approval
@@ -70,7 +70,7 @@ git commit -s
 
 ## Communication
 
-Please feel free to connect with us through the [issue tracker](https://github.com/contextforge-org/contextforge-plugins-framework/issues).
+Please feel free to connect with us through the [issue tracker](https://github.com/contextforge-org/cpex/issues).
 
 ## Setup
 

README.md

@@ -1,17 +1,17 @@
 <div>
-  <img alt="ContextForge Plugin Extensibility Framework (CPEX) logo" src="https://github.com/contextforge-org/contextforge-plugins-framework/blob/main/docs/images/cpex_v1.png?raw=true" height=100">
+  <img alt="ContextForge Plugin Extensibility Framework (CPEX) logo" src="https://github.com/contextforge-org/cpex/blob/main/docs/images/cpex_v1.png?raw=true" height=100">
 </div>
 
 # CPEX — ContextForge Plugin Extensibility Framework
 
 <i>A composable enforcement framework for AI agents and toolchains.</i>
 
-[![CI](https://github.com/contextforge-org/contextforge-plugins-framework/actions/workflows/ci.yml/badge.svg)](https://github.com/contextforge-org/contextforge-plugins-framework/actions/workflows/ci.yml)
+[![CI](https://github.com/contextforge-org/cpex/actions/workflows/ci.yml/badge.svg)](https://github.com/contextforge-org/cpex/actions/workflows/ci.yml)
 [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
 [![Python](https://img.shields.io/badge/python-3.11%2B-blue.svg)](https://www.python.org/downloads/)
 [![PyPI](https://img.shields.io/pypi/v/cpex.svg?color=blue)](https://pypi.org/project/cpex)
 
-> [**Read the project vision**](https://contextforge-org.github.io/contextforge-plugins-framework/docs/vision/) to learn why hooks, plugins, and policy are the path to agent security.
+> [**Read the project vision**](https://contextforge-org.github.io/cpex/docs/vision/) to learn why hooks, plugins, and policy are the path to agent security.
 
 ## What's CPEX?
 

cpex/tools/cli.py

@@ -44,7 +44,7 @@
 # Configuration defaults
 # ---------------------------------------------------------------------------
 LOCAL_TEMPLATES_DIR = Path(__file__).resolve().parent.parent / "templates"
-DEFAULT_TEMPLATE_URL = "https://github.com/contextforge-org/contextforge-plugins-framework.git"
+DEFAULT_TEMPLATE_URL = "https://github.com/contextforge-org/cpex.git"
 DEFAULT_AUTHOR_NAME = "<changeme>"
 DEFAULT_AUTHOR_EMAIL = "<changeme>"
 DEFAULT_PROJECT_DIR = Path("./.")

docs/content/docs/vision.md

@@ -17,7 +17,7 @@ Hooks are standardized interception points placed at every boundary where an age
 
 This architecture deploys identically across the stack, inside LLM proxies, agent frameworks, and gateways. Each layer runs its own plugins. Prompt injection detection at the proxy. Tool authorization at the gateway. Data loss prevention at the agent.
 
-![CPEX hooks deployed across the agent stack](/contextforge-plugins-framework/images/distributed_hooks_control_plane.png)
+![CPEX hooks deployed across the agent stack](/cpex/images/distributed_hooks_control_plane.png)
 
 ---
 
@@ -31,7 +31,7 @@ Enforcement is a three-layer problem.
 | **CMF** (Common Message Format) | What you evaluate. A protocol-agnostic context envelope carrying identity, security labels, delegation chains, and content. |
 | **APL** (Attribute Policy Language) | How you define policy. Declarative, attribute-based rules with explicit effects. |
 
-![Hooks, CMF, and APL form a unified enforcement stack](/contextforge-plugins-framework/images/overview_vision.png)
+![Hooks, CMF, and APL form a unified enforcement stack](/cpex/images/overview_vision.png)
 
 Hooks make enforcement **possible**. Policy makes it **usable**. Context makes it **correct**.
 
@@ -41,15 +41,15 @@ Hooks make enforcement **possible**. Policy makes it **usable**. Context makes i
 
 Different policy types require different enforcement points. CPEX provides hooks at every layer, from soft stylistic policies enforced at the prompt level to hard compliance requirements enforced at infrastructure boundaries.
 
-![Policy spectrum: each policy type maps to a different enforcement point](/contextforge-plugins-framework/images/policy_spectrum.png)
+![Policy spectrum: each policy type maps to a different enforcement point](/cpex/images/policy_spectrum.png)
 
 ---
 
 ## How It Works
 
 An application or framework invokes a hook at a critical operation boundary. The plugin manager dispatches registered plugins (sequentially, concurrently, or fire-and-forget) and returns a result. Plugins can **allow** execution to continue, **block** it with a violation, or **modify** the payload using copy-on-write isolation.
 
-![Plugin execution model: agent → middleware → hook → manager → plugins](/contextforge-plugins-framework/images/integration_execution_model.png)
+![Plugin execution model: agent → middleware → hook → manager → plugins](/cpex/images/integration_execution_model.png)
 
 The plugin manager handles registration, ordering, timeouts, error isolation, and payload chaining. You get a deterministic enforcement pipeline with no surprises.
 
@@ -67,7 +67,7 @@ CPEX is under active development. The current Python framework is production-rea
 
 - **Plugin catalog.** Discovery, versioning, and installation of plugins from registries. Multiple instances from a single manifest, managed through the CLI.
 
-See the [GitHub milestones](https://github.com/contextforge-org/contextforge-plugins-framework/milestones) and [open issues](https://github.com/contextforge-org/contextforge-plugins-framework/issues) for details.
+See the [GitHub milestones](https://github.com/contextforge-org/cpex/milestones) and [open issues](https://github.com/contextforge-org/cpex/issues) for details.
 
 ---
 
@@ -84,7 +84,7 @@ See the [GitHub milestones](https://github.com/contextforge-org/contextforge-plu
 
 CPEX is part of the [ContextForge](https://github.com/contextforge-org) ecosystem.
 
-- [CPEX Plugin Framework](https://github.com/contextforge-org/contextforge-plugins-framework) (this project)
-- [Contributing Guide](https://github.com/contextforge-org/contextforge-plugins-framework/blob/main/CONTRIBUTING.md)
+- [CPEX Plugin Framework](https://github.com/contextforge-org/cpex) (this project)
+- [Contributing Guide](https://github.com/contextforge-org/cpex/blob/main/CONTRIBUTING.md)
 
 Contributions, feedback, and plugin ideas are welcome. Open an issue or submit a pull request.

docs/hugo.toml

@@ -1,4 +1,4 @@
-baseURL = "https://contextforge-org.github.io/contextforge-plugins-framework/"
+baseURL = "https://contextforge-org.github.io/cpex/"
 languageCode = "en-us"
 title = "CPEX Documentation"
 theme = "hugo-book"
@@ -7,7 +7,7 @@ theme = "hugo-book"
   BookTheme = "auto"
   BookToC = true
   BookSection = "docs"
-  BookRepo = "https://github.com/contextforge-org/contextforge-plugins-framework"
+  BookRepo = "https://github.com/contextforge-org/cpex"
   BookSearch = true
   BookComments = false
   BookEditLink = '{{ .Site.Params.BookRepo }}/edit/main/docs/{{ .Path }}'

pyproject.toml

@@ -40,7 +40,7 @@ dependencies = [
 cpex = "cpex.tools.cli:main"
 
 [project.urls]
-Repository = "https://github.com/contextforge-org/contextforge-plugins-framework"
+Repository = "https://github.com/contextforge-org/cpex"
 
 [project.optional-dependencies]