@sudajs/cli 0.10.1 → 0.10.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sudajs/cli",
-  "version": "0.10.1",
+  "version": "0.10.3",
   "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": "2.5.0"
+    "@sudajs/theme-engine": "2.6.1"
   },
   "devDependencies": {
     "@tailwindcss/postcss": "^4.3.0",

package/templates/theme/AGENTS.md

@@ -9,6 +9,7 @@ Your job in a theme project is to create a complete, publishable theme with them
 - Keep `renderMode: "ssr"` in `src/manifest.ts`.
 - Keep source entries at `src/index.tsx`, `src/runtime.client.ts`, and `src/styles.css`.
 - Export a complete `ThemeModule` from `src/index.tsx`: `manifest`, `pageConfig`, `layoutConfig`, `defaultLayout`, and `starterPages`.
+- Starter page slugs preview at site-like root routes in `suda theme dev`: `home` is `/home`, `contact-us` is `/contact-us`. Do not use `/pages/...` as a preview route prefix.
 - Keep `pageConfig` focused on page content sections. Keep `layoutConfig` focused on shared site chrome such as root, header, page outlet, and footer.
 - Do not edit generated files under `dist/`; run `pnpm build` to regenerate them.
 - React, React DOM, Puck, and `@sudajs/theme-engine` are host-provided peers. Do not bundle private copies into the theme runtime.
@@ -106,6 +107,37 @@ Use the most specific field type available. A generic `text` field may pass type
 - Use Puck `resolveFields` only for heavier dynamic field changes that cannot be expressed with `visibleIf`.
 - Add field-level `ai.instructions`, `ai.required`, `ai.exclude`, `ai.stream`, or `ai.bind` when a prop needs generation guidance beyond its label and type. Use `ai.stream: false` for atomic values such as URLs that should not stream partially.
 
+## Contact form contract
+
+Themes must render the host-provided contact form from `metadata.contactForm`
+when they offer a contact section. The platform owns field metadata,
+validation, submissions, notifications, webhooks, permissions, and limits; the
+theme owns the public UI only.
+
+- Read the form through `getContactForm(puck?.metadata)` from
+  `@sudajs/theme-engine/runtime`.
+- `suda theme dev` passes a default contact form through `metadata.contactForm`
+  so contact sections can be developed and previewed locally without a project.
+- If there is no valid, enabled form configuration, render nothing for the form
+  area; do not show a public "contact form unavailable" fallback panel.
+- Style all five supported field types: `text`, `textarea`, `checkbox`,
+  `radio`, and `select`.
+- Style labels, inputs, submit button, success state, validation errors, and
+  responsive layout in the theme's visual language.
+- Only render placeholders supplied by the form setting. Do not invent default
+  placeholder text for any field type, including the empty option in `select`.
+- Submit to `contactForm.endpoint` with the field values; never hardcode
+  notification channels, webhook URLs, ICP records, or white-label branding in
+  the contact section.
+- Include hidden platform fields, including the honeypot field
+  `name={contactForm.honeypotField}`, as bare `<input type="hidden" />`
+  elements. Do not wrap any hidden field in an element, label, layout row, grid
+  item, or visual field component; future hidden tokens must follow the same
+  rule so they cannot disturb the theme's form layout.
+- Keep contact form layout accessible: every field has a label, keyboard focus
+  is visible, checkbox/radio options are grouped clearly, and error messages
+  are readable on mobile.
+
 ## AI metadata
 
 Every page component and layout component must declare useful `ai.instructions`. Missing component-level instructions fail `suda theme check` and block publish.