@adobe/design-data-spec 1.0.0 → 1.1.0

package/conformance/invalid/SPEC-039-syntax-error/dataset.json

@@ -0,0 +1,4 @@
+{
+  "tokens": [],
+  "components": []
+}

package/conformance/invalid/SPEC-039-syntax-error/expected-errors.json

@@ -0,0 +1,10 @@
+{
+  "layer": 2,
+  "errors": [
+    {
+      "rule_id": "SPEC-039",
+      "severity": "error",
+      "message_pattern": ".*"
+    }
+  ]
+}

package/conformance/invalid/SPEC-039-syntax-error/manifest.json

@@ -0,0 +1,5 @@
+{
+  "specVersion": "1.0.0-draft",
+  "foundationVersion": "1.0.0",
+  "include": ["not-a-valid-query"]
+}

package/conformance/invalid/SPEC-039-unknown-key/dataset.json

@@ -0,0 +1,4 @@
+{
+  "tokens": [],
+  "components": []
+}

package/conformance/invalid/SPEC-039-unknown-key/expected-errors.json

@@ -0,0 +1,10 @@
+{
+  "layer": 2,
+  "errors": [
+    {
+      "rule_id": "SPEC-039",
+      "severity": "error",
+      "message_pattern": ".*bogusKey.*"
+    }
+  ]
+}

package/conformance/invalid/SPEC-039-unknown-key/manifest.json

@@ -0,0 +1,5 @@
+{
+  "specVersion": "1.0.0-draft",
+  "foundationVersion": "1.0.0",
+  "include": ["component=button,bogusKey=foo"]
+}

package/conformance/valid/SPEC-039/dataset.json

@@ -0,0 +1,4 @@
+{
+  "tokens": [],
+  "components": []
+}

package/conformance/valid/SPEC-039/expected-errors.json

@@ -0,0 +1,4 @@
+{
+  "layer": 2,
+  "errors": []
+}

package/conformance/valid/SPEC-039/manifest.json

@@ -0,0 +1,10 @@
+{
+  "specVersion": "1.0.0-draft",
+  "foundationVersion": "1.0.0",
+  "include": [
+    "component=button",
+    "component=button,state=hover",
+    "property=color-*"
+  ],
+  "exclude": ["component=button,colorScheme!=light"]
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adobe/design-data-spec",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "Design Data Specification — prose, JSON Schemas, rule catalog, and conformance fixtures for Spectrum design data",
   "type": "module",
   "repository": {

package/rules/rules.yaml

@@ -383,3 +383,18 @@ rules:
     message: "Component '{component}' option '{option}' uses the obsolete `enum` keyword; replace with a `values` array so per-value lifecycle metadata can be expressed"
     spec_ref: spec/component-format.md#option-descriptor
     introduced_in: "1.0.0-draft"
+
+  - id: SPEC-039
+    name: manifest-query-parseable
+    severity: error
+    layer: 2
+    category: manifest
+    rfc: "#715"
+    assert: >
+      Each entry in 'manifest.include' and 'manifest.exclude' MUST parse as a valid query
+      expression per spec/query.md and MUST use only the supported query keys.
+      Entries that fail to parse, or that reference unsupported keys, are Layer 2 errors.
+      This rule lifts the deferred 'treat as opaque' clause from earlier 1.0.0-draft revisions.
+    message: "Manifest {array}[{idx}] failed to parse as a query: {error}"
+    spec_ref: spec/manifest.md#include--exclude
+    introduced_in: "1.0.0-draft"

package/spec/manifest.md

@@ -26,9 +26,11 @@ A manifest **MUST** conform to [`manifest.schema.json`](../schemas/manifest.sche
 
 ### `include` / `exclude`
 
-**NORMATIVE:** Entries **MUST** be non-empty strings.
+**NORMATIVE:** Each entry **MUST** be a non-empty string that parses as a valid query expression per [Query](query.md). An entry that fails to parse, or that references a key outside the [supported query key list](query.md#supported-keys), is a Layer 2 conformance error (SPEC-039 `manifest-query-parseable`).
 
-> **Note:** Query notation syntax is fully defined in [Query](query.md) and is normative for programmatic use. Its normative use in manifest `include`/`exclude` is deferred to a post-`1.0.0-draft` revision pending conformance fixtures; until then, implementations **MUST** treat manifest query values as opaque identifiers.
+See [Query — Formal grammar](query.md#formal-grammar) for the EBNF and [Query — Supported keys](query.md#supported-keys) for the normative list of allowed keys.
+
+> **Migration note (from earlier `1.0.0-draft` revisions):** Prior revisions instructed implementations to treat manifest query values as opaque identifiers. That clause is lifted as of this revision. Any manifest that uses non-query strings in `include`/`exclude` must be updated to use valid query notation; the SPEC-039 rule reports column-level parse errors to guide migration.
 
 ### `overrides`