@contentful/experience-design-system-cli 2.5.2 → 2.5.3-dev-build-727fd69.0

package/README.md

@@ -1,6 +1,8 @@
 # @contentful/experience-design-system-cli
 
-CLI for extracting, reviewing, generating, validating, and pushing Contentful Experience Design System component definitions.
+CLI for extracting, reviewing, generating, validating, and pushing Contentful Experience Design System component definitions into [Experience Orchestration (ExO)](https://www.contentful.com/help/experience-orchestration/).
+
+**Binary names:** `experiences` (primary), `exo` (alias), `experience-design-system-cli` (long-form). All three point to the same executable.
 
 ## Pipeline Overview
 

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentful/experience-design-system-cli",
-  "version": "2.5.2",
+  "version": "2.5.3-dev-build-727fd69.0",
   "description": "Contentful Experiences design system import CLI",
   "license": "MIT",
   "type": "module",

package/dist/src/apply/api-client.js

@@ -48,12 +48,8 @@ export class ImportApiClient {
         };
     }
     async validateToken() {
-        // /users/me is the canonical "is this token valid" endpoint — it doesn't enforce
-        // space-membership rules that don't apply to the design-systems API path, so it
-        // doesn't false-positive 401 for tokens that are entitled to call import endpoints
-        // but lack the role assignments public CMA's SpacesController/EnvironmentsController
-        // require. Per-space/per-org authorization is enforced by the design-systems API itself
-        // on the actual preview/apply call.
+        // /users/me is the canonical token-validity endpoint — avoids space-membership
+        // false positives that don't apply to the design-systems API authorization path.
         const url = `${this.host}/users/me`;
         const res = await request(url, { token: this.token });
         if (res.status === 401) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentful/experience-design-system-cli",
-  "version": "2.5.2",
+  "version": "2.5.3-dev-build-727fd69.0",
   "description": "Contentful Experiences design system import CLI",
   "license": "MIT",
   "type": "module",
@@ -32,7 +32,7 @@
     "react-dom": "^18.3.1",
     "ts-morph": "^27.0.2",
     "typescript": "^5.9.3",
-    "@contentful/experience-design-system-types": "2.5.2"
+    "@contentful/experience-design-system-types": "2.5.3-dev-build-727fd69.0"
   },
   "devDependencies": {
     "@tsconfig/node24": "^24.0.3",

package/skills/generate-components.md

@@ -109,7 +109,7 @@ Exactly **6** valid types:
 | `token` | Design-token-linked prop — requires `token_kind` |
 | `boolean` | Boolean toggle props (visible, disabled, enabled, etc.) |
 
-> **IMPORTANT: No `number` type.** The EMA Phase 2 API only supports the `String` design property variant for numeric values. All numeric props must use `cdf_type: "string"` with the number as a string default (e.g. `"0"`, `"100"`). Boolean props can now use `cdf_type: "boolean"` directly.
+> **IMPORTANT: No `number` type.** The design-systems API only supports the `String` design property variant for numeric values. All numeric props must use `cdf_type: "string"` with the number as a string default (e.g. `"0"`, `"100"`). Boolean props can now use `cdf_type: "boolean"` directly.
 
 > **Avoid `link` type for simple URL props.** Props named `href`, `url`, or holding plain URL strings → `cdf_type: "string"`, `cdf_category: "content"`. Reserve `link` for props that hold a reference to another Contentful entry.
 
@@ -337,7 +337,7 @@ Before emitting any tool calls, verify:
 7. `required` values are JSON booleans, not strings
 8. Framework internals (`ref`, event handlers, test IDs) are excluded — `className`, `style`, and `styles` are classified as `string` design props; discrete positional/geometric props (`top`, `bottom`, `left`, `right`, `rotation`, etc.) are also classified
 9. No `cdf_type: "link"` used — `link` is reserved and rejected by the CLI parser
-10. No `cdf_type: "number"` used — this is not a valid P2 type; use `"string"` with numeric defaults. `cdf_type: "boolean"` IS valid — use it for boolean toggle props.
+10. No `cdf_type: "number"` used — this is not a supported type; use `"string"` with numeric defaults. `cdf_type: "boolean"` IS valid — use it for boolean toggle props.
 
 After the run completes, the developer can validate the pipeline output with: