dyrected 2.5.53 → 2.5.56

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dyrected",
-  "version": "2.5.53",
+  "version": "2.5.56",
   "type": "module",
   "files": [
     "dist"
@@ -16,9 +16,9 @@
     "jiti": "^2.7.0",
     "prettier": "^3.2.5",
     "prompts": "^2.4.2",
-    "@dyrected/core": "^2.5.53",
-    "@dyrected/sdk": "^2.5.53",
-    "@dyrected/knowledge": "^0.2.10"
+    "@dyrected/core": "^2.5.56",
+    "@dyrected/knowledge": "^0.2.10",
+    "@dyrected/sdk": "^2.5.56"
   },
   "devDependencies": {
     "@types/fs-extra": "^11.0.4",

package/dist/utils/ai-rules-template.d.ts

@@ -1,2 +0,0 @@
-export declare function buildAiRules(): string;
-//# sourceMappingURL=ai-rules-template.d.ts.map

package/dist/utils/ai-rules-template.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ai-rules-template.d.ts","sourceRoot":"","sources":["../../src/utils/ai-rules-template.ts"],"names":[],"mappings":"AAAA,wBAAgB,YAAY,IAAI,MAAM,CAyZrC"}

package/dist/utils/ai-rules-template.js

@@ -1,411 +0,0 @@
-export function buildAiRules() {
-    return `# Dyrected AI Rules
-
-> This is the canonical instruction file for AI coding agents working with Dyrected.
-> The Dyrected CLI also creates tool-specific pointer files so supported agents load it automatically.
->
-> Full documentation: https://docs.dyrected.com
-
----
-
-## Before writing any code
-
-1. Read https://docs.dyrected.com before writing any integration code
-2. Check the installed package version and its exported types — do not assume API shape from memory
-3. Use only APIs that exist in the installed version; if the docs and the package disagree, use the package
-4. Read the existing \`dyrected.config.ts\` before suggesting any schema change
-5. Never invent field types, hook names, config options, or API methods
-
----
-
-## Core imports
-
-\`\`\`ts
-import { defineCollection, defineGlobal, defineConfig } from '@dyrected/core'
-import { DyrectedClient } from '@dyrected/sdk'
-\`\`\`
-
----
-
-## Available field types
-
-\`text\`, \`textarea\`, \`richText\`, \`number\`, \`boolean\`, \`date\`, \`datetime\`, \`time\`,
-\`email\`, \`url\`, \`icon\`, \`json\`, \`select\`, \`multiSelect\`, \`radio\`,
-\`relationship\`, \`image\`, \`object\`, \`array\`, \`blocks\`, \`row\`, \`join\`
-
-Do not invent field types that are not in this list.
-
-Docs: https://docs.dyrected.com/docs/concepts/fields
-
----
-
-## Never do these things
-
-- **Never use \`client.collections\`** — the only correct entry point is \`client.collection('slug')\`
-- **Never add custom auth or session middleware on admin routes** — Dyrected handles authentication internally; adding your own breaks the dashboard
-- **Never define \`email\` or \`password\` fields on an \`auth: true\` collection** — they are injected automatically
-- **Never delete a field from the config** — existing documents store data under that key; removing it orphans the data permanently
-- **Never rename a field directly** — use \`renameTo\` for a lazy, zero-downtime migration (see Schema Evolution below)
-- **Never add a new field to an existing collection without \`defaultValue\`** — existing documents need a safe read fallback
-- **Never use function callbacks in \`admin.condition\`** if the project uses Dyrected Cloud — use Jexl string expressions instead; functions are stripped on cloud sync
-
----
-
-## Schema evolution
-
-Full guide: https://docs.dyrected.com/docs/concepts/schema
-
-### Renaming a field safely
-
-\`\`\`ts
-{
-  name: 'fullName',   // new name
-  type: 'text',
-  renameTo: 'name',   // old name — fallback on read until all docs are resaved
-}
-\`\`\`
-
-Remove \`renameTo\` once all documents in production have been resaved under the new name.
-
-### Indexing a field for fast queries
-
-\`\`\`ts
-{ name: 'slug', type: 'text', unique: true, promoted: true }
-\`\`\`
-
-After adding \`promoted: true\`, run \`npx @dyrected/cli sync:schema\` (Cloud) or restart the server (self-hosted).
-Supported types: \`text\`, \`number\`, \`boolean\`, \`date\`, \`datetime\`.
-
----
-
-## Zero-state resilience
-
-Always write frontend data fetches with \`initialData\` fallbacks so the page renders when the backend
-is unreachable or the collection is empty.
-
-\`\`\`ts
-const { docs } = await client.collection('posts').find({ initialData: [] })
-const settings  = await client.global('site-settings').get({ initialData: { siteName: 'My Site' } })
-\`\`\`
-
----
-
-## Relationships and depth
-
-Docs: https://docs.dyrected.com/docs/concepts/relationships | https://docs.dyrected.com/docs/concepts/depth
-
-A \`relationship\` field stores the ID of a document in another collection (the owning side).
-A \`join\` field is a virtual reverse lookup — it stores nothing; it queries the other collection at read time.
-
-\`\`\`ts
-// relationship — stores an ID
-{ name: 'author', type: 'relationship', relationTo: 'users' }
-{ name: 'tags',   type: 'relationship', relationTo: 'tags', hasMany: true }
-
-// join — virtual reverse lookup (no storage)
-{
-  name: 'posts',
-  type: 'join',
-  collection: 'posts',  // the collection to look in
-  on: 'author',         // the relationship field on that collection
-  limit: 20,
-}
-\`\`\`
-
-Control how many levels of relationships are hydrated with \`depth\`:
-
-- \`depth: 0\` — return IDs only
-- \`depth: 1\` (default) — hydrate direct relationships; nested ones remain IDs
-- \`depth: 2\` — hydrate two levels deep
-
-Use \`depth: 0\` on list pages to keep payloads small. Use \`depth: 1\` (the default) when you need related field values.
-
----
-
-## Auth collections
-
-Docs: https://docs.dyrected.com/docs/concepts/auth-model
-
-\`auth: true\` turns a collection into an authentication provider. Dyrected automatically injects
-\`email\` (required, unique) and \`password\` (hashed, never returned in responses) — do not define them yourself.
-
-\`\`\`ts
-export const Users = defineCollection({
-  slug: 'users',
-  auth: true,
-  fields: [
-    { name: 'name', type: 'text' },
-    { name: 'role', type: 'select', options: ['member', 'editor', 'admin'] },
-  ],
-})
-\`\`\`
-
-Generated endpoints (all under \`/dyrected/api/{slug}/\`): \`login\`, \`logout\`, \`me\`, \`refresh-token\`,
-\`forgot-password\`, \`reset-password\`, \`invite\`, \`accept-invite\`, \`first-user\`, \`init\`.
-
-The admin dashboard uses a **separate** auth collection by convention. Define it as:
-
-\`\`\`ts
-export const Admins = defineCollection({
-  slug: '__admins',
-  auth: true,
-  fields: [],  // email + password are automatic
-})
-\`\`\`
-
-Do not mix app user auth and admin auth in the same collection unless you explicitly want editors to log into both.
-
----
-
-## Upload collections
-
-Docs: https://docs.dyrected.com/docs/guides/file-uploads
-
-\`upload: true\` turns a collection into a media library. Dyrected automatically injects \`filename\`,
-\`mimeType\`, \`url\`, \`filesize\`, \`width\`, \`height\`, and \`blurhash\`.
-
-\`\`\`ts
-export const Media = defineCollection({
-  slug: 'media',
-  upload: {
-    allowedMimeTypes: ['image/*'],
-    maxFileSize: 5_000_000,         // bytes
-    imageSizes: [
-      { name: 'thumbnail', width: 300, height: 300, crop: 'cover' },
-      { name: 'card',      width: 800 },
-    ],
-  },
-  fields: [
-    { name: 'alt', type: 'text' },
-  ],
-})
-\`\`\`
-
----
-
-## Dynamic options (select / multiSelect / radio)
-
-Docs: https://docs.dyrected.com/docs/concepts/dynamic-options
-
-Three ways to populate options — pick the right one:
-
-| Approach | Where it runs | Use when |
-|---|---|---|
-| Static array | — | Fixed list known at build time |
-| Server-side resolver (async function) | Server | DB queries, API keys, user-filtered lists, caching |
-| \`admin.hooks.options\` (UI hook) | Browser | Instant dependent/cascading dropdowns |
-
-\`\`\`ts
-// Server-side resolver — runs on the server, never sent to the browser
-{
-  name: 'category',
-  type: 'select',
-  options: async ({ db }) => {
-    const result = await db.find({ collection: 'categories' })
-    return result.docs.map(c => ({ label: c.name, value: c.id }))
-  },
-}
-
-// Client-side UI hook — runs in the browser, instant, no network round-trip
-{
-  name: 'region',
-  type: 'select',
-  options: [],
-  admin: {
-    hooks: {
-      options: ({ siblingData }) =>
-        siblingData.country === 'us'
-          ? [{ label: 'California', value: 'CA' }, { label: 'New York', value: 'NY' }]
-          : [],
-    },
-  },
-}
-\`\`\`
-
----
-
-## Conditional fields
-
-Docs: https://docs.dyrected.com/docs/admin/configuration#condition--conditional-fields
-
-Use \`admin.condition\` to show or hide a field based on sibling values. Use Jexl string expressions
-(not functions) for cloud compatibility:
-
-\`\`\`ts
-// Only show 'scheduledAt' when status is 'scheduled'
-{
-  name: 'scheduledAt',
-  type: 'datetime',
-  admin: {
-    condition: 'status == "scheduled"',
-  },
-}
-
-// Complex logic
-{
-  name: 'salePrice',
-  type: 'number',
-  admin: {
-    condition: 'onSale == true && price > 0',
-  },
-}
-\`\`\`
-
----
-
-## Custom field components and component slots
-
-Docs: https://docs.dyrected.com/docs/admin/configuration
-
-### Custom field input
-
-Replace any field's default input with a custom component. Declare a unique string key in the config:
-
-\`\`\`ts
-{
-  name: 'brandColor',
-  type: 'text',
-  admin: {
-    component: 'products.brandColor',
-  },
-}
-\`\`\`
-
-Register the component in your \`<DyrectedAdmin>\` wrapper:
-
-\`\`\`tsx
-// React / Next.js
-<DyrectedAdmin components={{ fields: { 'products.brandColor': BrandColorPicker } }} />
-
-// Vue / Nuxt
-<DyrectedAdmin :components="{ fields: { 'products.brandColor': BrandColorPicker } }" />
-\`\`\`
-
-The component receives \`value\`, \`onChange\`, \`field\`, \`path\`, \`disabled\`, and \`collection\` as props.
-
-### Component slots (dashboard and collection pages)
-
-Inject custom panels into the dashboard or collection list pages by declaring slot keys in the config
-and providing the matching components to \`<DyrectedAdmin>\`:
-
-\`\`\`ts
-// dyrected.config.ts
-defineConfig({
-  admin: {
-    components: ['dashboard.analytics'],   // slot key
-  },
-  ...
-})
-\`\`\`
-
-\`\`\`tsx
-<DyrectedAdmin
-  components={{
-    slots: { 'dashboard.analytics': AnalyticsDashboard }
-  }}
-/>
-\`\`\`
-
----
-
-## Intent → pattern
-
-Translate plain-language goals to the correct Dyrected pattern. Make the decision yourself
-— do not ask the developer to choose between Dyrected concepts.
-
-| If the user wants to…                                              | Use this pattern |
-|--------------------------------------------------------------------|------------------|
-| Auto-generate a slug from a title                                  | \`beforeChange\` collection hook (server) + \`admin.hooks.onChange\` on the slug field (live preview) |
-| Validate data before saving                                        | \`beforeChange\` collection hook — throw to abort |
-| Run logic after a document is saved                                | \`afterChange\` collection hook — never \`await\` slow ops inline; use \`.catch()\` |
-| Send a webhook or email when content changes                       | \`afterChange\` collection hook |
-| Revalidate a Next.js / Nuxt page after a save                     | \`afterChange\` collection hook posting to the revalidation endpoint |
-| Only admins can see a field                                        | Field-level \`access: { read: ({ user }) => user?.roles?.includes('admin') ?? false }\` |
-| Different roles can edit different fields                          | Field-level \`access.update\` |
-| Restrict who can create / edit / delete                            | Collection-level \`access\` config |
-| Track who created or changed a document                            | \`audit: true\` on the collection |
-| Content approval / draft-publish flow                              | \`workflow: publishingWorkflow()\` on the collection |
-| Guard a workflow transition                                        | \`workflow.hooks.beforeTransition\` — throw to cancel |
-| Notify someone after a workflow state change                       | \`workflow.hooks.afterTransition\` |
-| Different content per site (multi-tenant)                          | \`siteId\` on the collection + \`beforeRead\` hook to scope queries |
-| Share content across all sites                                     | \`shared: true\` on the collection |
-| Show a dependent dropdown based on another field (instant)         | \`admin.hooks.options\` on the dependent select field |
-| Populate a dropdown from a database query or external API          | Server-side \`options\` async resolver function |
-| Show a live computed value in the admin form                       | \`admin.hooks.onChange\` on the output field |
-| Show or hide a field based on another field's value                | \`admin.condition\` with a Jexl string expression |
-| Query or sort a field efficiently at scale                         | \`promoted: true\` on the field, then run \`sync:schema\` |
-| One fixed set of content (site name, logo, tagline…)               | \`defineGlobal\` |
-| Multiple entries the client can add or remove                      | \`defineCollection\` |
-| Flexible page layouts (hero, cards, testimonials…)                 | \`blocks\` field — one block definition per layout type |
-| Seed default content on first run                                  | \`initialData\` on the collection or global |
-| Reference a document in another collection                         | \`relationship\` field with \`relationTo: 'slug'\` |
-| Store multiple references (tags, categories…)                      | \`relationship\` field with \`hasMany: true\` |
-| Show all related documents on the other side (reverse lookup)      | \`join\` field with \`collection\` and \`on\` |
-| Fetch a document with its related data populated                   | Use \`depth: 1\` (default) on the query |
-| Allow users to log in to the app                                   | \`auth: true\` on a collection |
-| Separate admin login from app user login                           | Define a \`__admins\` collection with \`auth: true\` |
-| Allow file / image uploads                                         | \`upload: true\` (or an upload config object) on a collection |
-| Replace the default input for a field with a custom component      | \`admin.component\` string key + register in \`<DyrectedAdmin>\` |
-| Inject a custom panel into the dashboard or a collection page      | Component slots in \`admin.components\` config + register in \`<DyrectedAdmin>\` |
-
----
-
-## Canonical recipe: generate a slug from a title
-
-When the developer asks for automatic URLs, friendly URLs, or a slug derived from a title, implement both layers below. The server hook guarantees API writes are correct; the Admin hook gives editors immediate feedback.
-
-\`\`\`ts
-const toSlug = (value: unknown) =>
-  String(value ?? '')
-    .toLowerCase()
-    .trim()
-    .replace(/[^a-z0-9]+/g, '-')
-    .replace(/(^-|-$)/g, '')
-
-export const Posts = defineCollection({
-  slug: 'posts',
-  hooks: {
-    beforeChange: [({ data, operation }) => {
-      if (operation === 'create' || data.title !== undefined) {
-        return { ...data, slug: toSlug(data.title) }
-      }
-      return data
-    }],
-  },
-  fields: [
-    { name: 'title', type: 'text', required: true },
-    {
-      name: 'slug', type: 'text', required: true, unique: true, promoted: true,
-      admin: { hooks: { onChange: ({ siblingData }) => toSlug(siblingData.title) } },
-    },
-  ],
-})
-\`\`\`
-
-Do not implement only the browser hook: API-created documents would bypass it. Do not implement only the server hook when editors need to see the resulting URL while typing.
-
----
-
-## Access control
-
-Docs: https://docs.dyrected.com/docs/concepts/access-control
-
-- Create the smallest set of permissions needed for the approved use case
-- Editors may access only the content they are approved to edit
-- Do not grant delete or publish access unless explicitly required
-- Enforce access in the server-side config — not only by hiding controls in the Admin UI
-
----
-
-## Working approach
-
-- Work in small verified batches — no more than three related content areas at a time
-- Verify lint, types, and build pass before moving to the next batch
-- Fix a failing batch before starting new content types
-- Ask plain-language questions when you need clarification:
-  e.g. "Should the client be able to add more items, or only edit the ones already there?"
-  Never ask: "Should this be a collection or a global?"
-- Use the intent → pattern table above to make technical decisions without asking the developer
-`;
-}
-//# sourceMappingURL=ai-rules-template.js.map

package/dist/utils/ai-rules-template.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ai-rules-template.js","sourceRoot":"","sources":["../../src/utils/ai-rules-template.ts"],"names":[],"mappings":"AAAA,MAAM,UAAU,YAAY;IAC1B,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuZR,CAAC;AACF,CAAC"}