epismo 1.23.1 → 1.24.0

package/README.md

@@ -90,6 +90,19 @@ epismo case brief set CASE_ID --content "Waiting for launch approval."
 
 A Brief is one current sentence for a case. Closing the case does not remove it, and an archived case cannot be changed. Case reads include it when present. Read it through `case get`, set it with `case brief set`, delete it with `case brief delete`, or generate it from current case evidence with `case brief generate`. Generation runs synchronously and charges token-priced credits to the case billing account; set and delete are update operations costing 2 credits each to the acting user's active workspace, or personal account when no workspace is selected. Reviews do not update the Brief. Set requires non-empty content.
 
+## Case sources
+
+Link external evidence to a case and read its saved content with `case get`.
+Slack threads require a connected Slack account in the selected workspace.
+
+```sh
+epismo case source link CASE_ID --url 'https://acme.slack.com/archives/C123/p1234567890123456'
+epismo case get CASE_ID
+```
+
+Run `epismo source --help` for get, refresh, and unlink commands, and use
+command-level help for access requirements and credit costs.
+
 ## Playbook access
 
 Use `visibility` and explicit editors instead of a raw ACL:
@@ -100,7 +113,9 @@ epismo playbook access set PLAYBOOK_ID --visibility public --editors USER_ID,TEA
 epismo playbook owner transfer PLAYBOOK_ID --owner-id WORKSPACE_OR_USER_ID
 ```
 
-`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. Only the owner (including workspace owners and admins for a workspace-owned playbook) can 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 transfer`.
+`public` permits published reads only. The Playbook owner and workspace owners/admins retain implicit edit access and need no explicit `--editors` grant. Every workspace member can read published workspace-owned Playbooks; other members need an explicit user or team editor grant to edit them. Editors can change visibility and collaborators while retaining at least one team or another user as an explicit editor. Only owner managers can remove all additional sharing, archive a Playbook, or archive a historical version. Any member may create a Playbook owned by their workspace, or move a personally owned private Playbook into it with `playbook owner transfer`.
+
+Case editors can change public/private visibility and collaborators while retaining at least one team or another user as an explicit editor. Only the current Case assignee can remove all additional sharing or archive the Case. Access changes must preserve every task assignee's edit access. The dedicated `playbook access get` remains owner-manager-only, and `case access get` remains current-assignee-only; editors can inspect collaborators with the normal `playbook get` or `case get` before replacing sharing.
 
 Run `epismo --help` for command groups, or append `--help` to any group or command for its options.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "epismo",
-  "version": "1.23.1",
+  "version": "1.24.0",
   "description": "Native CLI for Epismo. Continue work across people and AI agents; JSON for terminals, scripts, and workflows.",
   "type": "module",
   "license": "Apache-2.0",