scribe-cms 0.0.16 → 0.0.20

package/README.md

@@ -71,6 +71,9 @@ on every type without declaring them. Redirects live in `content/<type>/_redirec
   Constraints go in the options (not chained Zod methods):
   `field.relation("glossary", { multiple: true, max: 8, optional: true })`.
   Validated by `scribe validate`, dereferenced with `related()`.
+- `field.asset(options?)` — a file reference (web path into `assets.dir`):
+  `field.asset({ dir: "/try-on/garments", formats: ["webp"], maxKB: 150 })`.
+  Validated by `scribe validate`, resolved to a served URL at load time.
 
 ### 3. Read content
 
@@ -113,10 +116,17 @@ scribe translate --direct      # per-page API calls at full price, immediate res
 scribe translate --resume      # pick up pending batch jobs from an interrupted run
 scribe translate --dry-run     # show the worklist without calling the API
 scribe history blog my-post fr # EN snapshot timeline for one document
+scribe delete blog my-post     # delete an entry + its reference cascade (--dry-run, --yes)
 scribe studio                  # read-only local admin UI
 scribe export-static           # raw MDX files for static hosting / crawlers
 ```
 
+`scribe delete <type> <slug>` prints the full impact plan (cascading deletes,
+reference detaches, asset files, store rows, and any blockers), then asks for
+confirmation. `--dry-run` prints the plan and stops; `--yes` skips the prompt.
+A blocked deletion (a `restrict` reference or a required single relation) exits
+non-zero without touching anything. See [Entry deletion](./docs/deletion.md).
+
 Translated output is checked before it is stored: the returned MDX body must
 parse and the frontmatter must re-validate against your Zod schema, so a bad
 model response fails the command instead of reaching production. Interactive