@docyrus/animaguru 0.31.0 → 0.32.1

package/README.md

@@ -158,7 +158,7 @@ animaguru files list PROJECT_ID
 animaguru files export PROJECT_ID --output forest-cast.zip
 ```
 
-`jobs wait` waits for the specified job only. A drawing may queue follow-up animation jobs; inspect `jobs list` and wait for those before exporting. Jobs continue on the server if the CLI exits. `files export` refuses to overwrite a file. `projects rename PROJECT_ID --name "New name"` and `projects delete PROJECT_ID --yes` manage the library. `projects move PROJECT_ID --to OTHER_PROJECT_ID --characters SLUG,SLUG --assets ASSET_ID --avatars GROUP_ID` moves characters (with all their animations), saved assets and the project's own avatars to another project you can write to, without regenerating anything (CLI 0.16.0). `models PROJECT_ID --video-model heygen/heygen-video-1` sets the defaults for future jobs. Image generation follows staff-managed main and backup routes and has no user model selector.
+`jobs wait` waits for the specified job only. A drawing may queue follow-up animation jobs; inspect `jobs list` and wait for those before exporting. Jobs continue on the server if the CLI exits. CLI 0.32.0 adds `jobs cancel PROJECT_ID JOB_ID --yes`: a project runs its jobs one at a time, and this cancels a queued job, or stops a running one at its next check on the provider, so a stuck job no longer holds up the rest. Credits it already spent stay spent. `files export` refuses to overwrite a file. `projects rename PROJECT_ID --name "New name"` and `projects delete PROJECT_ID --yes` manage the library. `projects move PROJECT_ID --to OTHER_PROJECT_ID --characters SLUG,SLUG --assets ASSET_ID --avatars GROUP_ID` moves characters (with all their animations), saved assets and the project's own avatars to another project you can write to, without regenerating anything (CLI 0.16.0). `models PROJECT_ID --video-model heygen/heygen-video-1` sets the defaults for future jobs. Image generation follows staff-managed main and backup routes and has no user model selector.
 
 Generation and reference imports require `--yes`, which authorizes credit spending. Read estimates from `projects get` before submitting. Estimates are ranges; actual provider usage is recorded to your own balance. Paid generation needs configured production provider bindings and secrets.
 
@@ -547,6 +547,19 @@ animaguru motion get skeleton-list-swipe --write animations/launch/src/scenes
 
 Then call the entry function from `Film.build()`, for example `skeletonListSwipe(this, { at: 4 })`. `--write` refuses to replace an existing scene (pass `--force`) and keeps shared modules that already exist.
 
+## Film templates
+
+An Individual Pro or Team workspace can save an applied film as a template on a project's Animations tab, then start new films from it. `template list` uses the selected cloud workspace (`--workspace personal` or `--workspace TEAM_ID` overrides it). `template install` copies a template into a video workspace as a new film folder; the film is then yours to change, and later changes to the template do not reach it.
+
+```sh
+animaguru template list
+animaguru template get TEMPLATE_ID
+animaguru template install TEMPLATE_ID                      # animations/<the template's film name>
+animaguru template install TEMPLATE_ID --name summer-launch # animations/summer-launch
+```
+
+Install refuses an existing film folder, checks every file's SHA-256 and moves the film into place only when it is complete. A template saved from a newer video workspace than yours needs a new workspace (`animaguru create workspace`). Read `production/template-brief.md` in the installed film for what it was made for. MCP provides `list_film_templates`.
+
 ## Brand kits
 
 Use saved personal or team brands across films. `brands list`, `create` and `research` use the selected cloud workspace; `--workspace personal` or `--workspace TEAM_ID` overrides it for that command. Commands taking a brand ID check access to that brand's workspace.