@sudajs/cli 0.12.4 → 0.13.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sudajs/cli",
-  "version": "0.12.4",
+  "version": "0.13.0",
   "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": "5.0.0"
+    "@sudajs/theme-engine": "5.1.0"
   },
   "devDependencies": {
     "@tailwindcss/postcss": "^4.3.0",

package/templates/theme/AGENTS.md

@@ -367,6 +367,12 @@ platform. In the section render function, call
 with the exact posts field key. Never import Prisma, call platform APIs, or
 query the database from theme code.
 
+When rendering posts returned by `getPostResource`, build links from the
+platform-provided `post.url` first. If it is missing, derive the URL only from
+`post.slug` as `/posts/${encodeURIComponent(post.slug)}`; if neither exists,
+use `#`. Do not guess alternate fields such as `href`, `path`, `permalink`,
+`postUrl`, or `canonicalUrl`.
+
 Do not add `resourceQuery: { type: "posts" }` or
 `resource_query: { type: "posts" }`. Do not assume the field must be named
 `query`. A section may have only one top-level posts field; do not nest posts
@@ -588,7 +594,7 @@ Good component instructions explain:
 - Frequency: whether it should appear once, multiple times, or only near another section.
 - Composition: required neighboring content or local blocks, when relevant.
 
-- For icons, expose props with `{ type: "icon" }`, type values as `SudaLucideIconName`, render them with `SudaLucideIcon` from `@sudajs/theme-engine/runtime`, and store canonical Lucide names such as `"rocket"` or `"mouse-pointer-click"` (not `"lucide-rocket"`). Do not keep theme-local icon maps, emoji/icon switch statements, or custom SVG icon registries unless the theme truly needs a bespoke non-Lucide graphic.
+- For icons, expose props with `{ type: "icon" }`, type values as `SudaLucideIconName`, render them with `SudaLucideIcon` from `@sudajs/theme-engine/icons`, and store canonical Lucide names such as `"rocket"` or `"mouse-pointer-click"` (not `"lucide-rocket"`). Do not keep theme-local icon maps, emoji/icon switch statements, or custom SVG icon registries unless the theme truly needs a bespoke non-Lucide graphic.
 - Add optional field-level `ai.instructions`, `ai.required`, or `ai.exclude` when a prop needs generation guidance beyond its label and type.
 - Use `ai.exclude: true` only for structural or editor-only components, and still provide instructions explaining why AI must not generate them. `PageOutlet` is the standard example.
 

package/templates/theme/src/sections.tsx

@@ -1,8 +1,11 @@
-import type { SudaComponentConfig, SudaLucideIconName } from "@sudajs/theme-engine";
+import type { SudaComponentConfig } from "@sudajs/theme-engine";
+import {
+  SudaLucideIcon,
+  type SudaLucideIconName,
+} from "@sudajs/theme-engine/icons";
 import {
   getPostResource,
   resolveAsset,
-  SudaLucideIcon,
   type ThemePostResourceQuery,
   type ThemeRenderMetadata,
 } from "@sudajs/theme-engine/runtime";
@@ -245,6 +248,8 @@ export const FeaturedPosts: SudaComponentConfig<FeaturedPostsProps> = {
       fieldKey: "postList",
     });
     const posts = resource.posts;
+    const postHref = (post: (typeof posts)[number]) =>
+      post.url || (post.slug ? `/posts/${encodeURIComponent(post.slug)}` : "#");
     return (
       <section className="__SUDA_THEME_KEY__-section">
         <h2>{title}</h2>
@@ -258,7 +263,7 @@ export const FeaturedPosts: SudaComponentConfig<FeaturedPostsProps> = {
                 </p>
                 <h3>{post.title}</h3>
                 <p>{post.excerpt}</p>
-                <a href={post.url}>{post.title}</a>
+                <a href={postHref(post)}>{post.title}</a>
               </article>
             ))
           ) : (