@sudajs/cli 0.12.3 → 0.12.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sudajs/cli",
-  "version": "0.12.3",
+  "version": "0.12.4",
   "type": "module",
   "bin": {
     "suda": "./bin/suda.js"
@@ -34,7 +34,7 @@
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
     "zod": "^3.24.1",
-    "@sudajs/theme-engine": "4.0.2"
+    "@sudajs/theme-engine": "5.0.0"
   },
   "devDependencies": {
     "@tailwindcss/postcss": "^4.3.0",

package/templates/theme/AGENTS.md

@@ -139,7 +139,7 @@ Field source of truth:
   generation reliable.
 - Use `description`, `placeholder`, and `visibleIf` only when they help the
   editor or AI choose the right value.
-- Suda extended field types are `url`, `icon`, `font`, `menu`, `color`,
+- Suda extended field types are `url`, `icon`, `color`,
   `range`, `spacing`, `media`, `image`, `video`, and `posts`. These are valid
   in `fields` and are normalized by `@sudajs/theme-engine`.
 
@@ -189,8 +189,6 @@ fields: {
   download: { type: "media", kind: "file", label: t("common.fields.file") },
   icon: { type: "icon", label: t("common.fields.icon") },
   accentColor: { type: "color", label: t("common.fields.color") },
-  font: { type: "font", label: t("common.fields.font") },
-  links: { type: "menu", label: t("common.fields.menu") },
   spacing: { type: "spacing", label: t("common.fields.spacing") },
 
   // Dynamic post lists. Use this only on page sections that intentionally
@@ -492,11 +490,11 @@ radius, shadows, or spacing.
 - Section props may expose semantic choices such as `tone`, `variant`,
   `columns`, `mediaPosition`, `showImage`, or `spacing`. Map those choices to
   the existing design tokens and shared CSS classes.
-- Do not add raw `color`, `font`, `spacing`, `radius`, or `shadow` fields to a
+- Do not add raw `color`, typography, `spacing`, `radius`, or `shadow` fields to a
   section just because the CSS has a value. Expose a design token field only
   when the user should intentionally customize that value per component
   instance. Otherwise, keep the value in the theme CSS.
-- Use `color`, `font`, and `spacing` field types only for real editor-facing
+- Use `color` and `spacing` field types only for real editor-facing
   design controls. Use `select`/`radio` for named variants that are already
   part of the theme design system.
 - Local blocks inside `blockSlots` inherit the host section's design system.
@@ -534,10 +532,11 @@ Use the most specific field type available. A generic `text` field may pass type
 
 - Always use `url` for links and routes, including anchors, `mailto:` links, and external URLs. Do not use `text` for href-like props.
 - Use `image` for images, `video` for videos, and `media` only when the same prop intentionally accepts mixed media.
-- Use `color` for color values, `icon` for icon names, `font` for font selections, `range` for bounded numbers, `spacing` for spacing tokens, and `menu` for navigation items.
+- Use `color` for color values, `icon` for icon names, `range` for bounded numbers, and `spacing` for spacing tokens.
+- Use `select` for typography choices and `array`/`object` fields for navigation lists.
 - Use `select` or `radio` for fixed choices. Keep option values stable, short, and serializable.
 - Use `array` for repeatable items and `object` for grouped settings. Keep nested field names aligned with the prop shape and `defaultProps`.
-- Use `textarea` for multi-sentence copy. Use `text` only for short labels, headings, slugs, names, or plain strings that are not URLs, media, colors, icons, fonts, or menus.
+- Use `textarea` for multi-sentence copy. Use `text` only for short labels, headings, slugs, names, or plain strings that are not URLs, media, colors, icons, typography choices, or navigation lists.
 - Use `t(...)` for every editor-facing `label` in components, fields, nested
   `arrayFields` / `object.fields`, local blocks, and option lists. Add matching
   keys to `src/locales/en.json` at the same time.