zinkee 0.1.23 → 0.1.25

package/.claude/settings.local.json

@@ -43,7 +43,11 @@
       "Bash(git -C /home/guillermo/dev/cli branch --show-current)",
       "Bash(git -C /home/guillermo/dev/cli diff --stat)",
       "Bash(git fetch *)",
-      "Bash(pnpm exec *)"
+      "Bash(pnpm exec *)",
+      "Bash(echo \"=== exit $? \\(grep\\) ===\")",
+      "Bash(grep -rn \"resourceType\" src/)",
+      "Bash(grep -rn \"automation-folders/\\\\${\\\\|/automations:move\\\\|{folderId}/automations\" src/)",
+      "Bash(grep -rn \"navigation resources move.*--type\\\\|resourceType\" docs/ README.md)"
     ]
   }
 }

package/AGENTS.md

@@ -36,6 +36,7 @@ Use this order when reasoning about behavior:
 - `teamspace`
 - `displays`
 - `automations`
+- `document-templates`
 
 ## Implementation Shape
 

package/README.md

@@ -17,6 +17,7 @@ Implemented command groups:
 - `teamspace`
 - `displays`
 - `automations`
+- `document-templates`
 
 ## Requirements
 
@@ -337,7 +338,7 @@ zinkee --json logs list <schema-slug> <record-uuid>
 
 ## Navigation
 
-Organize schemas into database folders.
+Organize schemas into database folders. The navigation menu holds databases, so only schemas can be moved here.
 
 ```bash
 # List folders with contents
@@ -347,13 +348,16 @@ zinkee --json navigation folders list
 zinkee navigation folders create --name "CRM" --order 1
 
 # Move a schema into a folder
-zinkee navigation resources move <schema-uuid> --type SCHEMA --to "CRM"
+zinkee navigation resources move <schema-uuid> --to "CRM"
 
-# Delete folder (resources move back to root silently)
+# Move a schema back to the workspace root
+zinkee navigation resources move <schema-uuid> --to 00000000-0000-0000-0000-000000000000
+
+# Delete folder (schemas move back to root silently)
 zinkee navigation folders delete "CRM"
 ```
 
-Root folder cannot be deleted.
+Only schemas can be moved (schedules and sub-schemas follow their parent schema). Root folder cannot be deleted; its UUID is always `00000000-0000-0000-0000-000000000000`.
 
 ---
 
@@ -387,6 +391,27 @@ zinkee teamspace resources publish projects --to "Other Folder"
 
 Displays are dashboards composed of widgets that visualize data from schemas.
 
+### Display folders
+
+Organize displays into folders in the displays menu. Folders are flat (name only) and only displays can be moved into them.
+
+```bash
+# List display folders (non-root folders plus the root bucket)
+zinkee --json displays folders list
+
+# Create a folder
+zinkee displays folders create --name "Executive Dashboards"
+
+# Rename a folder
+zinkee displays folders update "Executive Dashboards" --name "Executive Dashboards (2026)"
+
+# Move a display into a folder
+zinkee displays folders move <display-uuid> --to "Executive Dashboards"
+
+# Delete a folder (its displays move back to the root folder)
+zinkee displays folders delete "Executive Dashboards"
+```
+
 ### Creation flow
 
 1. Create the display
@@ -656,6 +681,58 @@ zinkee --json automations connections list
 
 ---
 
+## Document templates
+
+Document templates group reusable files (e.g. Word/Excel masters) that automations can render against a record via the `generate_document` action. Names must be unique within the workspace; the `<template>` argument accepts a UUID or an exact name. The `<asset>` argument requires a UUID.
+
+### Typical lifecycle
+
+1. Create an empty template
+
+```bash
+zinkee --json document-templates create --name "Quarterly report"
+```
+
+2. Upload one or more asset files
+
+```bash
+zinkee --json document-templates assets add "Quarterly report" ./requirements.docx
+zinkee --json document-templates assets add "Quarterly report" ./contract.docx --name "Customer Contract"
+```
+
+3. List and inspect
+
+```bash
+zinkee --json document-templates list
+zinkee --json document-templates get "Quarterly report"
+```
+
+4. Rename / replace assets / remove
+
+```bash
+zinkee --json document-templates update "Quarterly report" --name "Annual report"
+zinkee --json document-templates assets delete <template-uuid> <asset-uuid>
+zinkee --json document-templates delete <template-uuid>
+```
+
+### Download asset bytes
+
+`download` streams raw bytes — use `--output` to write to disk (required when combined with `--json`):
+
+```bash
+zinkee --json document-templates assets download <template-uuid> <asset-uuid> --output ./contract.docx
+zinkee document-templates assets download <template-uuid> <asset-uuid> > contract.docx
+```
+
+### Notes
+
+- `get` is a client-side helper: the backend has no get-one endpoint, so the CLI filters the list response. Use `list` if you want everything in one call.
+- The `assets` returned by list/get include a relative `link` ready to call directly (it already includes both the templateId and assetId path segments).
+- Deleting a template removes its asset files from storage; record fields that referenced previously generated documents are not modified.
+- Use `--json --example document-templates <subcommand>` for canonical examples.
+
+---
+
 ## Discovery
 
 ```bash
@@ -665,5 +742,6 @@ zinkee --json displays list
 zinkee --json automations list
 zinkee --json automations plugins list
 zinkee --json automations connections list
+zinkee --json document-templates list
 zinkee --example <command path>
 ```