epismo 1.10.0 → 1.12.0

package/README.md

@@ -39,6 +39,15 @@ The npm package contains a dependency-free JavaScript launcher and all supported
 
 ## Quick start
 
+Browse Public Playbooks without an account:
+
+```sh
+epismo playbook list
+epismo playbook get PLAYBOOK_ID
+```
+
+Log in for search, private data, and writes:
+
 ```sh
 epismo login
 epismo workspace list
@@ -49,6 +58,8 @@ epismo playbook init --title Onboarding > playbook.json
 epismo playbook create --definition @playbook.json
 ```
 
+`epismo workspace checkout <workspace-id>` starts a hosted subscription checkout. If the workspace has a cancellation scheduled for the end of its current billing period, it resumes that subscription instead of creating a second one.
+
 ## Playbook access
 
 Use `visibility` and explicit editors instead of a raw ACL:
@@ -60,6 +71,18 @@ epismo playbook access set PLAYBOOK_ID --visibility public --editors USER_ID,TEA
 
 `public` permits published reads only. Editors can read and edit Playbook content; the owner is implicit and is not included in `--editors`. Owner managers, including Workspace Owners and Admins for a Workspace-owned Playbook, manage access and archive Playbooks or historical Versions.
 
+## Cases and handoffs
+
+Start a Case, append timeline Records, connect dependent workflows, and explore the DAG:
+
+```sh
+epismo case start --title "Customer Onboarding"
+epismo case record append CASE_ID --kind result --content "Completed setup"
+epismo case handoff FIRST_CASE_ID --to-case-id SECOND_CASE_ID
+epismo case handoff graph CASE_ID --scope connected
+epismo case record list CASE_ID --scope ancestors
+```
+
 Run `epismo --help` for command groups, or append `--help` to any group or command for its options.
 
 Use `epismo examples` for common workflows, `epismo doctor` to inspect local setup, and `epismo completion zsh` (or `bash`, `fish`, `powershell`) to install shell completion.
@@ -119,7 +142,7 @@ EPISMO_WORKSPACE=acme epismo case list
 
 Workspace references accept an exact ID or unique handle. The effective workspace is chosen in this order: `--workspace`, `EPISMO_WORKSPACE`, a workspace-scoped token, then the saved default workspace. A scoped token cannot grant access outside its scope.
 
-`--dry-run` previews any command that changes remote or local state without sending a request, opening an authorization or checkout flow, or changing local configuration. This includes creates, updates, publishes, draft saves, assignments, records, stars, aliases, membership changes, archive/delete/revoke/close operations, and login/logout or workspace-selection changes. Read-only commands reject `--dry-run` instead of silently ignoring it. In an interactive terminal, especially impactful operations still ask for confirmation during a real run; pass `--yes` to skip that prompt in scripts that allocate a TTY.
+`--dry-run` previews any command that changes remote or local state without sending a request, opening an authorization or checkout flow, or changing local configuration. This includes creates, updates, publishes, draft saves, assignments, records, handoffs, stars, aliases, membership changes, archive/delete/revoke/close operations, and login/logout or workspace-selection changes. Read-only commands reject `--dry-run` instead of silently ignoring it. In an interactive terminal, especially impactful operations still ask for confirmation during a real run; pass `--yes` to skip that prompt in scripts that allocate a TTY.
 
 `--input` also works on list/search commands for agent workflows; there it supplies query parameters rather than a request body.
 
@@ -127,6 +150,8 @@ Workspace references accept an exact ID or unique handle. The effective workspac
 
 `epismo login` opens a browser-based OAuth login. With `--email`, it automatically uses your organization SSO when available, otherwise it prompts for an email code.
 
+`epismo playbook list` and UUID-based `epismo playbook get` work before login, as shown above, for Public Playbooks. The CLI creates a stable random `anonymousId` in its config for analytics and fair-use rate limiting; it is not an authentication credential. Search, aliases, private data, and writes still require login.
+
 For CI or other non-interactive use, create a workspace-scoped token and pass it with `EPISMO_TOKEN`:
 
 ```sh

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "epismo",
-  "version": "1.10.0",
+  "version": "1.12.0",
   "description": "Dependency-free CLI for discovering, authoring, and coordinating reusable AI Playbooks.",
   "type": "module",
   "license": "Apache-2.0",