Trigger docs deployment for docs/* changes too (#25)

* Trigger docs deployment for docs/* changes too
* Replace annoying '—' (em space) that comes from letting LLMs re-write your content 🤦
* Adjust some comments in mcpm registry code

Author: peteski22

.github/workflows/deploy-docs.yaml

@@ -5,6 +5,7 @@ on:
     branches: [main]
     paths:
       - "cmd/**"
+      - "docs/**"
   workflow_dispatch:
 
 permissions:

README.md

@@ -1,6 +1,8 @@
 # mcpd
 
-**mcpd** is a CLI and local daemon that helps developers and infrastructure teams manage [Model Context Protocol](https://github.com/mozilla-ai/mcp-spec) (MCP) servers declaratively — with the same experience locally and in production.
+**mcpd** is a CLI and local daemon that helps developers and infrastructure teams manage 
+[Model Context Protocol](https://github.com/mozilla-ai/mcp-spec) (MCP) servers declaratively, 
+with the same experience locally and in production.
 
 > Built by [Mozilla AI](https://mozilla.ai)
 

docs/execution-context.md

@@ -30,4 +30,4 @@ These values apply at runtime and are separate from your project-specific `.mcpd
 ```
 
 !!! warning "Manual Changes"
-    The Execution Context Configuration file is automatically updated by `mcpd config` commands — you shouldn't edit it by hand unless absolutely necessary.
+    The Execution Context Configuration file is automatically updated by `mcpd config` commands, you shouldn't edit it by hand unless absolutely necessary.

docs/index.md

@@ -4,7 +4,9 @@
 
 ---
 
-`mcpd` is a toolchain and runtime developed by [Mozilla AI](https://mozilla.ai) that simplifies the configuration, execution and integration of Model Context Protocol (MCP) servers with your agentic application — across local development and production environments.
+`mcpd` is a toolchain and runtime developed by [Mozilla AI](https://mozilla.ai) that simplifies the configuration, 
+execution and integration of Model Context Protocol (MCP) servers with your agentic application.
+It is intended to provide the same experience across local development and production environments.
 
 It removes the friction of cross-language server orchestration, secrets management, version pinning, and lifecycle control.
 
@@ -32,7 +34,7 @@ Traditional agent frameworks often embed complex subprocess logic, brittle start
   One command: `mcpd daemon`. Starts and manages all servers behind the scenes.
 
 🧰 **Intuitive SDK Integration**  
-  The Python `mcpd_sdk` makes calling tools feel like native function calls — no HTTP, STDIO, or SSE boilerplate.
+  The Python `mcpd_sdk` makes calling tools feel like native function calls; no HTTP, STDIO, or SSE boilerplate.
   Even easier for users of [any-agent](https://github.com/mozilla-ai/any-agent) via `.agent_tools()`.
 
 🚀 **Seamless Local-to-Prod Transition**  

docs/requirements.md

@@ -2,9 +2,9 @@
 
 To use `mcpd`, ensure the following tools are installed:
 
-- [`uv` / `uvx`](https://docs.astral.sh/uv/getting-started/installation/) — for running `uvx` Python packages
-- [`npx` / `npm` / `NodeJS`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) — for running JavaScript/TypeScript packages
-- [Go](https://go.dev/doc/install) — only required for building and developing `mcpd`
+- [`uv` / `uvx`](https://docs.astral.sh/uv/getting-started/installation/) - for running `uvx` Python packages
+- [`npx` / `npm` / `NodeJS`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) - for running JavaScript/TypeScript packages
+- [Go](https://go.dev/doc/install) - only required for building and developing `mcpd`
 
 !!! note "Internet Connectivity"
     `mcpd` requires internet access to contact package registries and to allow MCP servers access to the internet if required when running.

internal/provider/mcpm/registry.go

@@ -299,10 +299,7 @@ func convertInstallations(src map[string]Installation) map[runtime.Runtime]packa
 // It returns a map where keys are supported runtime identifiers (e.g., "npx", "uvx") and values are
 // the corresponding plain package names used to execute the server.
 //
-// Only installations where the command matches a supported runtime are included.
-// Additionally, the installation must use a standard execution format—plain package names like "some-package" or
-// "some-package@version". Non-standard forms such as git URLs, Python scripts, or direct file paths
-// are ignored.
+// Only installations where the command matches a supported runtime may be included.
 // An error is returned if a supported runtime is found but a valid package name cannot be extracted.
 func (r *Registry) supportedRuntimePackageNames(installations map[string]Installation) (map[runtime.Runtime]string, error) {
 	result := make(map[runtime.Runtime]string)
@@ -332,6 +329,8 @@ func (r *Registry) supportedRuntimePackageNames(installations map[string]Install
 // URLs, git references, and script files (".py").
 //
 // This function enforces a strict format, ensuring only plain package names are accepted.
+// e.g. "some-package" or "some-package@version".
+// Non-standard forms such as git URLs, Python scripts, or direct file paths are ignored.
 // Returns an error if no suitable package name is found.
 func extractPlainPackage(rt runtime.Runtime, args []string) (string, error) {
 	for _, arg := range args {