feat: component visual recipes, renderer, and static explorer site

.ai/inventory.json

@@ -108,6 +108,24 @@
       "llms": false,
       "summary": "Figma variables import, export, and diff plugin."
     },
+    {
+      "path": "sdk/plugins/site",
+      "kind": "crate",
+      "audience": "consumer",
+      "lifecycle": "active",
+      "published": false,
+      "llms": false,
+      "summary": "Static component explorer site generator."
+    },
+    {
+      "path": "sdk/plugins/site/assets",
+      "kind": "package",
+      "audience": "consumer",
+      "lifecycle": "active",
+      "published": false,
+      "llms": false,
+      "summary": "Browser assets (HTML and visual runtime) embedded by the site generator."
+    },
     {
       "path": "sdk/tui",
       "kind": "package",

.ai/skills/beads-jira-sync/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: beads-jira-sync
+description: >-
+  Syncs beads issues to the Jira DNA project with import-beads.js from the standalone
+  beads-jira-import repo. Covers dry-run, state-file backup, live sync, initiative labels on
+  epics, and bead/Jira key lookup. Use for the weekly beads to Jira sync, linking an epic to a
+  DNA initiative, or finding the Jira key for a bead id.
+---
+
+<!-- Copyright 2026 Adobe. All rights reserved. -->
+
+# Beads → Jira sync
+
+`import-beads.js` lives in the local `beads-jira-import` checkout (no remote; extracted from `adobe-mcp-servers` `src/corp-jira/scripts/`). Fix bugs in the TypeScript source and rebuild `dist/` before a live sync. Below, `$BJI` is that checkout (e.g. `~/Projects/beads-jira-import`).
+
+## Safety rules
+
+* **Never run `--help`.** Unknown flags are ignored and the script falls through to a LIVE sync.
+* Safe modes: `--lookup <ids>`, `--dry-run`, `--discover`. Check the argument parser before using any other flag.
+* Always `--dry-run` first, and back up `$BJI/scripts/beads-jira-map.json` before a live sync.
+* Known issue: `--dry-run` can fail with ENOBUFS when the beads export exceeds 1 MiB (bead `cr71`).
+* Known issue: nested epics with both a parent and an initiative label overwrite the same Parent Link field (bead `vd61`).
+
+## Weekly sync
+
+1. `bd dolt pull` so the export is current.
+2. Back up state: `cp -f $BJI/scripts/beads-jira-map.json $BJI/scripts/beads-jira-map.json.bak`.
+3. Dry run: `node $BJI/dist/scripts/import-beads.js --dry-run`. Review the preview with the user.
+4. After approval, run live: `node $BJI/dist/scripts/import-beads.js`.
+5. Report created/updated issues and any diagnostics.
+
+## Sprints
+
+The sync assigns sprints itself (`operations/sprints.ts`): closed beads go to the sprint containing their close date, `in_progress` beads go to the active sprint, open beads stay in the backlog. Jira rejects adds to closed sprints, so beads closed in an already-closed sprint are skipped. The board is the project's first scrum board, or `BEADS_JIRA_BOARD_ID`. Open and close sprints in Jira first so the active sprint is the current one.
+
+## Initiative linking
+
+New beads get `bd create --parent <epic>`. Work with no labeled ancestor epic never reaches an initiative or a status update. The sync prints the count of beads closed in the last 30 days with no initiative; reparent them with `bd update <id> --parent <epic>`. Environment and personal-tooling tasks (MCP config, local TUI setup) are exempt.
+
+Only **Epics** link to Initiatives, through the `initiative:DNA-XXXX` label. One initiative per epic; omit the label if none fits.
+
+* New epic: `bd create -t epic -l initiative:DNA-XXXX ...`
+* Existing epic: `bd label add <epic-id> initiative:DNA-XXXX`
+
+Initiatives:
+
+| Key      | Theme                                  |
+| -------- | -------------------------------------- |
+| DNA-1522 | Adaptive support per platform          |
+| DNA-1520 | Multi-platform governance              |
+| DNA-1516 | Metrics                                |
+| DNA-1740 | Per-platform usage baselines           |
+| DNA-1741 | Connect Web/iOS/Android to design data |
+| DNA-1747 | AI-authored Spectrum 2 code            |
+| DNA-1748 | Documentation                          |
+| DNA-1796 | Design data authoring                  |
+
+## Lookup
+
+`node $BJI/dist/scripts/import-beads.js --lookup <bead-id or DNA-key>`
+
+Ad hoc Jira work (not bulk sync) uses the `corp-jira` MCP server tools.

.changeset/anatomy-definition-and-review.md

@@ -0,0 +1,24 @@
+---
+"@adobe/design-data-spec": minor
+"@adobe/spectrum-design-data": patch
+"@adobe/design-data-wasm": patch
+---
+
+Define what an anatomy part is and review the first five components against it.
+
+**Spec:**
+
+- `anatomy-format.md` says what counts as a part, how to name and nest parts, when a part
+  is required, and what is not anatomy. It adds a review checklist.
+- New optional `presentIn` lists the states a part is present in. Not allowed on a required part.
+- New optional `anatomyReview` on a component records `draft` or `reviewed`.
+- New info rule SPEC-073 lists components with relationships but no anatomy, or draft anatomy.
+- New error SPEC-074: a part's `presentIn` states must be declared on the component.
+- New error SPEC-075: a recipe's `visibleWhen.states` must agree with the part's `presentIn`.
+
+**Data:**
+
+- Button, action-button and badge anatomy are reviewed.
+- Button `label` is now optional. The focus indicator is state-only on all four.
+
+**WASM:** the validator includes SPEC-073 to SPEC-075.

.changeset/artifact-moves.md

@@ -0,0 +1,11 @@
+---
+"@adobe/design-data-spec": minor
+---
+
+Add the artifact-moves chapter: promoting and demoting one artifact between a platform
+and the foundation.
+
+- **spec/artifact-moves.md**: what can move, who decides, promotion criteria, the six steps,
+  the demotion notice period (same as deprecation), and proposed `lifecycle.moves` provenance.
+- **Proposed, not implemented**: rule SPEC-077 `artifact-single-owner` for half-finished moves.
+- **spec/index.md, spec/manifest.md**: link to the new chapter.

.changeset/button-static-color-recipe.md

@@ -0,0 +1,12 @@
+---
+"@adobe/spectrum-design-data": patch
+---
+
+Fix the Button visual recipe for static color black and white.
+
+- **label/icon**: static colors apply to primary and secondary; accent and negative stay white.
+- **accent/negative fill**: backgrounds require `style: fill`, so outline no longer gets a fill.
+- **focus ring**: static color uses transparent black or white 1000.
+- **disabled**: static color uses overlay 100 fill, 300 border and 400 content.
+- **hover/down**: static outline background is overlay 100; static border ignores gray hover.
+- **static outline border**: primary 800, secondary 300.

.changeset/checkbox-relationship-context-prefix.md

@@ -0,0 +1,24 @@
+---
+"@adobe/spectrum-design-data": patch
+"@adobe/design-data-spec": minor
+"@adobe/design-data-wasm": minor
+---
+
+Recipe lints and fixes for checkbox, switch and others; pressed scale includes nested parts.
+
+- **relationships**: strip the stray "S2 " prefix from contexts; add checkbox `Control`,
+  disabled and error contexts; scope selected switch and radio-button records with
+  `isSelected: true` (the schema allows boolean option values, the renderer maps them).
+- **visuals**: pressed parts scale nested children; checkbox `pressTarget`; `notVisual` option list.
+- **validate**: SPEC-066 to SPEC-070 warn on uncovered options and states, token selectors a
+  relationship covers, literals, deprecated tokens and focus ring names; SPEC-071 is info.
+  SPEC-072 flags a duplicated relationship whose token has a scale counterpart.
+  `recipe_lint_baseline` holds each recipe at its current warning count.
+- **spec**: authoring conventions in `component-visuals.md`; `notVisual` recipe field.
+- **relationships**: `scope.options` pick a default or the most specific override (arrays allowed);
+  badge colors, padding and fonts bind that way, shrinking its recipe by 1,600 lines.
+  `scope.options.state` adds states to the bound token.
+- **button, action-button**: colors, press perspective, hold-icon inset bind via relationships;
+  a render snapshot test covers every recipe; 103 duplicate records point at mobile tokens.
+- **focus-indicator**: the `focus-ring` anatomy, gap token and recipe parts are now
+  `focus-indicator` (legacy key `focus-ring-gap` kept).

.changeset/component-visual-recipes.md

@@ -0,0 +1,23 @@
+---
+"@adobe/spectrum-design-data": minor
+"@adobe/design-data-spec": minor
+"@adobe/design-data-wasm": minor
+---
+
+Add a draft component visual recipe format for rendering to SVG, PNG, and Figma.
+
+- **spec/component-visuals.md**: draft RFC and schema; `design-data:validate` checks recipes.
+- **action-button**: pilot recipe `visuals/action-button.json`; adds `progress`, `isPending`.
+- **sdk (core, cli)**: `render` makes SVG; `compile_recipe` pre-binds tokens.
+- **sdk/wasm**: `Dataset.renderScene` and `Dataset.renderSvg` render recipes in the browser.
+- **button**: `visuals/button.json` recipe (variant, style, state, static color); `down` state.
+- **spec and renderers**: container `stroke`, `relativeTo: "height"` radius, pressed scale-down.
+- **badge**: `visuals/badge.json` recipe, anatomy; drops the unused `isDisabled` option.
+- **renderers and site**: per-corner radius props, font weight names to numbers, label presence.
+- **sdk/plugins/site**: `design-data site --out <dir>` writes a static explorer (no WASM).
+- **sdk/plugins/figma**: `variable_names` maps tokens to Figma variable names offline.
+- **sdk/core**: scene token refs carry alias `chain`; press tokens are tracked.
+- **switch**: `visuals/switch.json` recipe, anatomy, `hideLabel`, and 15 color relationships.
+- **sdk/core, site**: nested box layout, `around` ring, `pressTarget`, component-scoped sizes.
+- **spec rules**: SPEC-060..063 check recipes against components (`validate --visuals-path`).
+- **checkbox**: `visuals/checkbox.json` recipe, anatomy, `box`/`dash` terms; `glyph` draws marks.

.changeset/figma-export-override-modes.md

@@ -0,0 +1,12 @@
+---
+"@adobe/design-data-tui": patch
+---
+
+Fix `design-data figma export --platform` dropping the other colour-scheme modes of an
+overridden token.
+
+- An override record carries `manifest.json` as its file, so the exporter grouped it apart from
+  its light and dark siblings and let it replace the whole variable.
+- Overrides now group with their foundation siblings; the three iOS seafoam tokens keep their
+  dark value.
+- Exports without `--platform` are unchanged.

.changeset/flowed-box-paints.md

@@ -0,0 +1,14 @@
+---
+"@adobe/design-data-spec": patch
+"@adobe/spectrum-design-data": patch
+"@adobe/design-data-wasm": patch
+---
+
+A box placed directly in a row now paints itself, so checkbox and switch no longer need a
+render-only `control` part.
+
+- Renderer and JS runtime read `fill`, `stroke` and `strokeWidth` on a flowed box.
+- Checkbox and switch drop `control`. The box and the track carry the size and hold the marks
+  and the handle. Rendered geometry, colors and press scale are unchanged.
+- Relationships that named `control` now name `box` (checkbox) or `track` (switch).
+- Checkbox and switch anatomy are now reviewed.

.changeset/option-constraints-matrix.md

@@ -0,0 +1,14 @@
+---
+"@adobe/design-data-wasm": patch
+---
+
+The component explorer (`design-data site`) now honors option constraints.
+
+- **Matrix:** combinations excluded by an `error` constraint are not rendered, and rows or columns
+  left empty are dropped. A note under the grid says what was left out and why, with the fix.
+  `advisory` combinations render with a footnote saying they have no distinct design.
+- **Pickers:** values that lead to an unsupported combination read "(not supported)", and a status
+  message under the pickers explains the current selection, with one-click fixes.
+- **Zoom view:** an unsupported selection shows the explanation instead of a render.
+- **sdk/plugins/site:** new `constraints.js` mirrors `sdk/core/src/constraints.rs`; a shared
+  fixture keeps the Rust and JS evaluations in lockstep.

.changeset/option-constraints-rules.md

@@ -0,0 +1,13 @@
+---
+"@adobe/design-data-spec": minor
+"@adobe/design-data-wasm": minor
+---
+
+Validate option constraints in the Rust SDK.
+
+- **SPEC-064** (error, Layer 2): every option name and value in a constraint's `when` / `require`
+  must be declared in the component's `options`. Silent when an option has no `values` list.
+- **SPEC-065** (warning, Layer 2): a visual recipe rule or relationship `scope.options` that
+  matches only combinations excluded by an `error` constraint.
+- **sdk/core**: new `constraints` module reads `component.constraints` into a typed model.
+- Conformance fixtures for both rules under `conformance/{valid,invalid}`.

.changeset/option-constraints.md

@@ -0,0 +1,11 @@
+---
+"@adobe/design-data-spec": minor
+"@adobe/spectrum-design-data": minor
+---
+
+Add `constraints` to the component format: if-then rules that limit valid option combinations.
+
+- **spec/option-constraints.md**: `when` / `require` / `severity` (`error` or `advisory`).
+- **component.schema.json**: optional `constraints` array. Layer 1 checks shape only; Layer 2
+  checks names and values.
+- **button, action-button, checkbox**: first constraints, taken from react-spectrum S2.

.changeset/platform-override-keeps-fields.md

@@ -0,0 +1,22 @@
+---
+"@adobe/design-data-spec": patch
+"@adobe/design-data-wasm": patch
+---
+
+A platform manifest override now keeps every field of the record it replaces.
+
+**Spec:**
+
+- `manifest.md` `overrides` now says what the code already did: the override replaces the
+  foundation record for that platform's graph (same key and uuid).
+- `query` returns one record per token.
+- Defines the in-memory markers `overriddenBy` and `overriddenFrom`. Legacy output omits them.
+
+**Core and WASM:**
+
+- An override no longer drops `$schema`, `$valueType`, `lifecycle`, `description` or
+  `conceptId`. It changes only `value` or `$ref`.
+- A replaced record carries `overriddenBy` (`{platform}` or `{manifest}`) and
+  `overriddenFrom` (the foundation value, kept even after several overrides).
+- Output with no platform is unchanged. With the iOS manifest, the three teal overrides
+  now keep their `$schema`, `uuid` and `private` fields.

.changeset/platform-recipe-check.md

@@ -0,0 +1,23 @@
+---
+"@adobe/design-data-spec": minor
+"@adobe/design-data-tui": patch
+"@adobe/design-data-wasm": patch
+---
+
+Check that visual recipes still resolve under a platform manifest.
+
+**Spec:**
+
+- New warning SPEC-076: every token or relationship binding a recipe resolves on the foundation
+  must also resolve once the platform manifest's cascade is applied.
+- New conformance fixture `invalid/SPEC-076`.
+
+**CLI:**
+
+- `design-data validate --platform <id> --visuals-path <dir>` runs SPEC-076 and names each binding
+  the platform drops. It reuses the render scene diagnostics.
+
+**Platforms:**
+
+- The iOS manifest no longer carries an `include` whitelist. It shipped only a few properties,
+  which dropped the height, padding, font-size and icon-size tokens recipes bind.

.changeset/platform-recipes-core.md

@@ -0,0 +1,22 @@
+---
+"@adobe/design-data-spec": minor
+"@adobe/design-data-tui": patch
+"@adobe/design-data-wasm": patch
+---
+
+Load platform-owned visual recipes and add `componentAliases`.
+
+**Spec:**
+
+- `manifest.schema.json` accepts `componentAliases` (string to string).
+- New error SPEC-081: an alias key must be a foundation component, its target must be declared in
+  the platform's `extensions/components/`, aliases must not chain or cycle, and a key must not
+  also be replaced there. New conformance fixture `invalid/SPEC-081`.
+
+**SDK core:**
+
+- A platform's `extensions/visuals/<component>.json` loads into `graph.visuals` with
+  `layer: Platform` and replaces the foundation recipe of the same name. A bad fragment or a
+  file name that differs from `component` is an error naming the file.
+- `TokenGraph::canonical_component` returns the alias target under the active platform. Render,
+  site and WASM do not call it yet.

.changeset/platform-recipes-spec-text.md

@@ -0,0 +1,14 @@
+---
+"@adobe/design-data-spec": minor
+---
+
+Spec text for platform-owned visual recipes (planned, not yet enforced).
+
+* `component-visuals.md`: platform recipes in `extensions/visuals/` replace the
+  foundation recipe whole; SPEC-079 and SPEC-080.
+* `manifest.md`: capability-matrix rows, the `extensions/visuals/` entry and the
+  planned `componentAliases` field (SPEC-081).
+* `artifact-moves.md`: a platform recipe moves with its component and alias.
+* `rules.yaml`: adds SPEC-079 (warning, an error one minor version later),
+  SPEC-080 (info) and SPEC-081 (error), all marked planned. SPEC-077 and 078
+  stay reserved by `artifact-moves.md`.

.changeset/render-platform-cascade.md

@@ -0,0 +1,18 @@
+---
+"@adobe/design-data-wasm": minor
+"@adobe/design-data-tui": patch
+---
+
+Render component visuals through a platform manifest.
+
+- `design-data render` and `design-data site` accept the global `--platform <id>` (or
+  `DESIGN_DATA_PLATFORM` / `default_platform`) and apply the Foundation to Platform cascade
+  before building scenes: tokens are filtered and overridden, and extension components,
+  relationships and tokens are layered in.
+- A recipe binding that does not resolve under a platform is reported as
+  `warning: platform '<id>': ...`. The site lists these in a panel instead of drawing nothing.
+- The site writes the platform into `data.json` and names it in the nav heading
+  ("Foundation" when none is selected).
+- WASM: `Dataset.applyPlatform(manifest)` applies a manifest with its `extensions` merged
+  inline, so `renderScene` and `renderSvg` render a platform build.
+- With no platform selected, output is unchanged.

.changeset/visual-recipe-array-conditions.md

@@ -0,0 +1,12 @@
+---
+"@adobe/design-data-spec": patch
+"@adobe/design-data-wasm": patch
+"@adobe/spectrum-design-data": patch
+---
+
+Recipe `when.options` conditions now accept an array of values, as the spec already described.
+
+- **sdk/core, site runtime**: an array matches when any value matches and counts as one condition.
+- **SPEC-061**: checks each element of an array condition against the option's declared values.
+- **spec**: component-visuals states that an array counts as one condition.
+- **button**: static color rules for primary and secondary share one entry with `variant: [...]`.

.changeset/wasm-visual-compile-solve.md

@@ -0,0 +1,8 @@
+---
+"@adobe/design-data-wasm": patch
+---
+
+Speed up `Dataset.renderScene` and `Dataset.renderSvg` by compiling each recipe once per
+component, size and mode and reusing it. Repeated renders are 30 to 55 times faster
+(button 6.5 to 0.21 ms, badge 5.0 to 0.11 ms, switch 7.8 to 0.14 ms). Scene and SVG output
+are unchanged.

.gitattributes

@@ -0,0 +1 @@
+sdk/plugins/site/assets/spectrum-controls.js linguist-generated=true -diff

.github/scripts/fixtures/platform-recipes-clean.json

@@ -0,0 +1,7 @@
+{
+  "errors": [{ "rule_id": "SPEC-081", "file": "m", "message": "bad alias" }],
+  "warnings": [
+    { "rule_id": "SPEC-080", "file": "x", "message": "replaces" },
+    { "rule_id": "SPEC-066", "file": "y", "message": "z" }
+  ]
+}