@sleekcms/sync 1.5.0 → 1.6.0

package/README.md

@@ -281,7 +281,7 @@ Models describe the shape of your content. They're JSON-like files with unquoted
 | `json` | Object or array |
 | `block(key)` | Embedded block object |
 | `stack` | Array of heterogeneous block objects; each item carries `_block: "<block_key>"` to name its block |
-| `entry(key)` | Entry object or slug reference |
+| `entry(key)` | Reference token `"<index>\|<text>"` — `index` is the entry's 0-based position in `content/entries/<key>+.json` (what binds); the optional `<text>` is the entry's opening content copied verbatim (a substring check, not a summary you write). Resolves to the entry object in templates |
 
 ---
 

package/dist/AGENT.md

@@ -279,7 +279,7 @@ Model fields declare both the editor type and the shape expected in content JSON
 | `block(key)` | Object matching that block's model; stored inline in the parent page/entry content and rendered with `blocks/<key>.ejs` |
 | `[block(key)]` | Array of block objects; each item matches the block model and renders with `blocks/<key>.ejs` |
 | `stack` | Array of heterogeneous block-shaped objects. Each item is `{ "_block": "<block_key>", ...fields_of_that_block }`. `_block` is the target block's key as a plain string; the remaining keys must match that block's model. Different items in the same stack may use different blocks. Stored inline; each item renders through its own `blocks/<key>.ejs`. The CMS resolves block keys to ids server-side — never write numeric ids. |
-| `entry(key)` / `[entry(key)]` | Slug string / array of slug strings in content JSON; entry object / array of entry objects in templates |
+| `entry(key)` / `[entry(key)]` | Reference token `"<index>\|<text>"` (or an array of them) in content JSON; entry object / array of entry objects in templates. `index` is the 0-based position of the target entry in its `content/entries/<key>+.json` list — that is what binds. `\|<text>` is optional: the **opening characters of that entry's content, copied verbatim** (matched as a substring — not a description you compose), used only to relocate the entry if the list shifted. You may write just the index (`"2"` or `2`). |
 | Group `{ ... }` | Nested object |
 | Collection `[{ ... }]` | Array of nested objects |
 
@@ -324,11 +324,11 @@ The content file at `content/pages/about.json`:
         "cta_label": "Contact us",
         "cta_link": "/contact"
     },
-    "tags": ["engineering", "design"]
+    "tags": ["0|Engineering", "2|Design"]
 }
 ```
 
-Here `hero` is embedded block data stored directly in the page content file. `image` and `hero.background` use the shortcut form — on save, the sync engine replaces each shortcut with a real image object (`{ "url": "...", "alt": "..." }`). Write the object form directly when you have a specific asset URL.
+Here `hero` is embedded block data stored directly in the page content file. `image` and `hero.background` use the shortcut form — on save, the sync engine replaces each shortcut with a real image object (`{ "url": "...", "alt": "..." }`). Write the object form directly when you have a specific asset URL. `tags` references entries by position — `"0|Engineering"` points at the first entry in `content/entries/tags+.json`, where `Engineering` is just the start of that entry's content copied verbatim (a substring check, not a description you write). The index is what binds on save; the text only helps relocate the entry if the list shifted, and a bare index (`"0"`) is also accepted.
 
 ### Markdown content files
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@sleekcms/sync",
-    "version": "1.5.0",
+    "version": "1.6.0",
     "description": "Edit SleekCMS sites locally — models, content, templates, images — with live two-way sync and AI agent support.",
     "keywords": [
         "sleekcms",