Register the edgecommons CLI as a tool; add docsPath for monorepo entries

components.json

@@ -249,6 +249,24 @@
         "s3",
         "edgecommons-sink"
       ]
+    },
+    {
+      "name": "edgecommons",
+      "repo": "edgecommons/edgecommons",
+      "docsPath": "cli/docs",
+      "language": "RUST",
+      "category": "tool",
+      "description": "The EdgeCommons CLI. One static binary that scaffolds components in four languages, validates their config and artifacts against the canonical schema, moves them between library versions, packages and releases them, and compiles a deployment definition into platform-native artifacts. Carries the templates and schema inside itself, so it works offline.",
+      "status": "beta",
+      "library": "edgecommons",
+      "topics": [
+        "edgecommons",
+        "cli",
+        "scaffolding",
+        "deployment",
+        "iiot",
+        "edgecommons-tool"
+      ]
     }
   ]
 }

registry.schema.json

@@ -46,6 +46,10 @@
           "pattern": "^[A-Za-z0-9_.-]+/[A-Za-z0-9_.-]+$",
           "description": "owner/name on GitHub, e.g. edgecommons/opcua-adapter"
         },
+        "docsPath": {
+          "type": "string",
+          "description": "Path to the entry's `docs/` folder within its repo, when it is not at the repo root. Needed for entries that ship from a monorepo - the `edgecommons` CLI lives at `cli/` inside the library repo, whose root `docs/` holds the library's own internal design docs. Omit for the usual one-repo-per-entry case."
+        },
         "language": {
           "type": "string",
           "enum": [