epismo 1.18.1 → 1.18.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/npm/vendor/darwin-amd64/epismo +0 -0
- package/npm/vendor/darwin-arm64/epismo +0 -0
- package/npm/vendor/linux-amd64/epismo +0 -0
- package/npm/vendor/linux-arm64/epismo +0 -0
- package/npm/vendor/windows-amd64/epismo.exe +0 -0
- package/npm/vendor/windows-arm64/epismo.exe +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -70,11 +70,11 @@ epismo playbook access set PLAYBOOK_ID --visibility public --editors USER_ID,TEA
|
|
|
70
70
|
epismo playbook owner PLAYBOOK_ID --owner-id WORKSPACE_OR_USER_ID
|
|
71
71
|
```
|
|
72
72
|
|
|
73
|
-
`public` permits published reads only. Editors can read and edit Playbook content; the owner, and every member of a Workspace-owned Playbook, are implicit and are not included in `--editors`. Workspace members can read and edit Playbooks owned by a Workspace they belong to. Owner managers, including Workspace Owners and Admins for a Workspace-owned Playbook, manage access, public visibility, and archive Playbooks or historical
|
|
73
|
+
`public` permits published reads only. Editors can read and edit Playbook content; the owner, and every member of a Workspace-owned Playbook, are implicit and are not included in `--editors`. Workspace members can read and edit Playbooks owned by a Workspace they belong to. Owner managers, including Workspace Owners and Admins for a Workspace-owned Playbook, manage access, public visibility, and archive Playbooks or historical versions. Any member may create a Playbook owned by a Workspace they belong to, or move a personally owned private Playbook into it with `playbook owner`.
|
|
74
74
|
|
|
75
75
|
## Cases and handoffs
|
|
76
76
|
|
|
77
|
-
Start a Case, append timeline
|
|
77
|
+
Start a Case, append timeline records, connect dependent workflows, and explore the DAG:
|
|
78
78
|
|
|
79
79
|
```sh
|
|
80
80
|
epismo case start --title "Customer Onboarding"
|
|
@@ -153,7 +153,7 @@ Workspace references accept an exact ID or unique handle. The effective workspac
|
|
|
153
153
|
|
|
154
154
|
`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.
|
|
155
155
|
|
|
156
|
-
`epismo playbook list`, UUID-based `epismo playbook get`, `epismo case get`, `epismo case popular`, `epismo case record list`, and `epismo case handoff graph` work before login for Public Playbooks and Public Cases. Public Case reads expose the current title, input,
|
|
156
|
+
`epismo playbook list`, UUID-based `epismo playbook get`, `epismo case get`, `epismo case popular`, `epismo case record list`, and `epismo case handoff graph` work before login for Public Playbooks and Public Cases. Public Case reads expose the current title, input, records, and readable handoffs; tasks, assignment, and collaborator identities remain restricted to work collaborators. `case get` includes the latest five records; pass its `records_next_cursor` to `case record list --cursor` with `--scope self` for older public records. Use `case popular --playbook-id <id> --lang ja,en` to filter discovery. 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, live Case work, and writes still require login.
|
|
157
157
|
|
|
158
158
|
For CI or other non-interactive use, create a workspace-scoped token and pass it with `EPISMO_TOKEN`:
|
|
159
159
|
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|