@astryxdesign/core 0.5.2-canary.d7bb4bf → 0.5.2-canary.de42f11

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astryxdesign/core",
-  "version": "0.5.2-canary.d7bb4bf",
+  "version": "0.5.2-canary.de42f11",
   "displayName": "Astryx Core",
   "description": "The component library. Accessible, themeable React components with built-in spacing, dark mode, and StyleX styling.",
   "author": "Meta Open Source",
@@ -661,7 +661,7 @@
     "react-dom": ">=19.0.0"
   },
   "devDependencies": {
-    "@astryxdesign/cli": "0.5.2-canary.d7bb4bf",
+    "@astryxdesign/cli": "0.5.2-canary.de42f11",
     "@babel/cli": "^8.0.4",
     "@babel/core": "^7.29.7",
     "@babel/preset-react": "^8.0.1",

package/src/Markdown/Markdown.spec.md

@@ -16,11 +16,11 @@ verified_by:
     packages/core/src/theme/themingTargets.test.ts,
     scripts/check-knowledge.mjs,
   ]
-families: []
+families: [family:navigation-destinations]
 design_specs: []
 architecture: [architecture:component-theming-surface]
 contributing: []
-system_specs: []
+system_specs: [spec:AST-005/DEC-1, spec:AST-005/DEC-2]
 ---
 
 # Markdown component contract
@@ -166,6 +166,12 @@ and this change preserves the existing spelling exactly.
 - `architecture:component-theming-surface` owns anatomy qualification, target
   mapping, target-capability state, composition boundaries, and compatibility for
   frozen targets.
+- `family:navigation-destinations` owns the shared accept/block result for parsed
+  links and every Astryx-owned navigation sink. `spec:AST-005/DEC-1` requires
+  Markdown navigation to remain conformant with Core link plumbing.
+- `spec:AST-005/DEC-2` keeps embedded-resource policy separate. Markdown may
+  reject a broader set of image/resource URLs without narrowing the shared
+  navigation contract.
 - Nested Astryx primitives retain ownership of their own anatomy and targets;
   Markdown owns the outer block targets listed here.
 

package/src/NavMenu/NavHeadingMenu.spec.md

@@ -18,7 +18,7 @@ verified_by:
     packages/core/src/theme/themingTargets.test.ts,
     scripts/check-knowledge.mjs,
   ]
-families: []
+families: [family:navigation-destinations]
 design_specs: []
 architecture:
   [
@@ -28,7 +28,7 @@ architecture:
     architecture:public-component-api,
   ]
 contributing: []
-system_specs: []
+system_specs: [spec:AST-005/DEC-1]
 ---
 
 # NavHeadingMenu component contract
@@ -173,7 +173,11 @@ owns the layer lifecycle and supplies the close callback through context.
   heading-provided close callback.
 - `architecture:public-component-api` owns the stable props and subcomponent
   surface; this documentation adds no API.
-- NavHeadingMenu has no current family contract.
+- `family:navigation-destinations` owns the shared accept/block result for a
+  NavHeadingMenuItem `href`; `spec:AST-005/DEC-1` requires native and
+  custom-router item paths to preserve that result.
+- NavHeadingMenu's current custom-router path inherits the `useLinkComponent`
+  adoption gap recorded by the family until the accepted implementation lands.
 
 ## Verification map
 

package/src/TreeList/TreeList.spec.md

@@ -16,7 +16,7 @@ verified_by:
     packages/core/src/theme/themingTargets.test.ts,
     scripts/check-knowledge.mjs,
   ]
-families: []
+families: [family:navigation-destinations]
 design_specs: []
 architecture:
   [
@@ -25,7 +25,7 @@ architecture:
     architecture:public-component-api,
   ]
 contributing: []
-system_specs: []
+system_specs: [spec:AST-005/DEC-1]
 ---
 
 # TreeList component contract
@@ -183,8 +183,11 @@ authorize a new target.
   surface; this documentation adds no API.
 - `architecture:interaction-modality` owns shared keyboard and pointer modality;
   TreeList continues to own its existing tree focus and activation behavior.
-- TreeList has no current family contract, and no unresolved family or runtime
-  record identifier is included.
+- `family:navigation-destinations` owns the shared accept/block result for a
+  TreeListItem `href`; `spec:AST-005/DEC-1` requires native and custom-router
+  item paths to preserve that result.
+- TreeList's current custom-router path inherits the `useLinkComponent` adoption
+  gap recorded by the family until the accepted implementation lands.
 
 ## Verification map