feat: split ExoMetadataProps into base and ExperienceMetadataProps [DX-987]

ExoMetadataProps no longer includes name — aligns with upstream MetadataSchema
used by ComponentType and Template. New ExperienceMetadataProps extends the base
with name? for variant labeling, mirroring upstream ExperienceMetadata.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: tylerpina

lib/common-types.ts

@@ -377,14 +377,21 @@ export interface MetadataProps {
 }
 
 /**
- * Metadata shape for ExO entities (ComponentType, Experience/View, Template).
+ * Base metadata shape for ExO entities (ComponentType, Template).
+ * Mirrors upstream MetadataSchema: tags and concepts only.
  * - tags: optional (upstream MetadataSchema.tags is z.optional as of SPA-3821)
  * - concepts: optional taxonomy concept links
- * - name: optional display name for variant labeling (SPA-3939)
  */
 export interface ExoMetadataProps {
   tags?: Link<'Tag'>[]
   concepts?: Link<'TaxonomyConcept'>[]
+}
+
+/**
+ * Extended metadata shape for Experience entities only.
+ * Adds name? for variant labeling (SPA-3939), mirroring upstream ExperienceMetadata.
+ */
+export interface ExperienceMetadataProps extends ExoMetadataProps {
   name?: string
 }
 

lib/entities/experience.ts

@@ -1,4 +1,4 @@
-import type { CursorPaginationParams, ExoMetadataProps, Link } from '../common-types'
+import type { CursorPaginationParams, ExperienceMetadataProps, Link } from '../common-types'
 import type {
   ComponentTypeViewport,
   DimensionedDesignPropertyValue,
@@ -49,7 +49,7 @@ type ExperienceCommonProps = {
   designProperties: Record<string, DimensionedDesignPropertyValue>
   dimensionKeyMap: ExperienceDimensionKeyMap
   contentBindings?: ExperienceContentBindings
-  metadata?: ExoMetadataProps
+  metadata?: ExperienceMetadataProps
   slots?: Record<string, Array<FragmentNode | InlineFragmentNode>>
 }