📖 [Docs]: Process-PSModule reference uses its canonical site

src/docs/Capabilities/index.md

@@ -27,7 +27,6 @@ the same spec-and-design shape as any other capability.
 | [Deployment](deployment/index.md) | How a change to managed resources is approved together with its effect and deployed exactly as approved — one spec, and one design for each combination of deploying a service provider from a CI/CD platform. |
 | [VS Code Extension Framework](vscode-extension-framework/index.md) | How a VS Code extension is built, tested, versioned, packaged, and published — one GitHub-native pipeline, opt-in from a template and a single settings file. |
 | [PowerShell on GitHub](powershell-on-github/index.md) | How we make GitHub a first-class platform for PowerShell through reusable modules, actions, and capability gaps we close over time. |
-| [Process-PSModule](process-psmodule/index.md) | The end-to-end PowerShell module pipeline — what it must guarantee and how it is built, alongside reference documentation for configuration and deployment. |
 | [Agentic Development](agentic-development/index.md) | The framework for org-scoped docs and memory repositories that give agents project-specific standards, working knowledge, and behavior. |
 
 <!-- INDEX:END -->

src/docs/Capabilities/powershell-on-github/design.md

@@ -32,7 +32,7 @@ The model combines two tracks:
 ## Current canonical references
 
 - PSModule initiative overview: ../../Initiatives/PSModule.md
-- Process-PSModule capability: ../../Capabilities/process-psmodule/index.md
+- [Process-PSModule documentation](https://psmodule.io/docs/Modules/Process-PSModule/)
 - Coding standards baseline: ../../Coding-Standards/index.md
 
 ## Planned evolution