epismo 1.25.1 → 1.25.3

package/README.md

@@ -69,6 +69,8 @@ epismo playbook create --definition '{"title":"Onboarding","steps":[]}'
 
 `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.
 
+See the [CLI guide](https://epismo.ai/en/docs/cli) for setup and workflow documentation.
+
 ## Cases and handoffs
 
 Start a case, append timeline records, connect dependent workflows, and explore the DAG:
@@ -86,26 +88,35 @@ epismo case get CASE_ID
 epismo case brief generate CASE_ID
 epismo case brief delete CASE_ID
 epismo case brief set CASE_ID --content "Waiting for launch approval."
+epismo case brief set CASE_ID --content "Waiting for launch approval." --details '{"needs":[{"text":"Launch approval","recordIds":[]}]}' --priority high
+epismo case brief set CASE_ID --priority urgent
+epismo case brief set CASE_ID --priority none
+epismo case list --status open --priority high
+epismo case list --priority none
 ```
 
-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.
+A Brief contains a summary sentence of up to 280 characters and optional DNA details: `decisions`, `needs`, and `actions`. Each category has up to three `{text, recordIds}` items, each with at most three supporting Record IDs from the same case. Details summarize evidence; they do not approve work or assign tasks. Closing the case does not remove it, and an archived case cannot be changed. Case reads include it when present; reading never generates it. Use `case brief set` with any of `--content`, `--details`, and `--priority`. Omitted fields are preserved; pass `--details '{}'` to clear DNA. Priority-only Briefs may have an empty summary. `case brief delete` removes the summary and details and clears Case priority, including when only priority is set. Generation runs synchronously, extracts supported DNA, and optionally assesses priority; receives all saved Brief values as prior context and may revise or remove them; a null DNA or priority result clears the corresponding field. It charges token-priced credits to the case billing account; set and delete cost 2 credits each to the acting user's active workspace, or personal account when no workspace is selected. Reviews do not update the Brief.
+
+Brief priority is `urgent`, `high`, `normal`, or `low`. Use `case brief set --priority` to edit it without changing the summary or DNA, including after close. Priority is read from `case.brief.priority`. Pass `--priority none` to clear it on writes or to select unset Cases on `case list`; omit the option to preserve it on writes or include all priorities on lists. The CLI converts `none` to the API's empty-string representation, including when passed through `--input`. Responses use enum numbers: `0` unset, `1` urgent, `2` high, `3` normal, `4` low. Generated priority needs concrete evidence; an absent urgency signal does not imply `normal`.
 
 ## 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.
+Slack threads and Discord messages/threads require a connected provider account
+in the selected workspace.
 For Google Docs, Sheets, or Slides, connect Google Drive and select the file in
-Epismo Web first, then link its URL. See [Google Drive setup](https://epismo.ai/en/docs/integrations/google-drive).
+Epismo Web first, then link its URL.
 
 ```sh
-epismo case source link CASE_ID --url 'https://acme.slack.com/archives/C123/p1234567890123456'
-epismo case source link CASE_ID --url 'https://docs.google.com/document/d/FILE_ID/edit'
+epismo case source link CASE_ID --url SOURCE_URL
 epismo case get CASE_ID
 ```
 
 Run `epismo case source --help` for get, refresh, and unlink commands, and use
 command-level help for access requirements and credit costs.
 
+Setup: [Slack](https://epismo.ai/en/docs/integrations/slack) · [Discord](https://epismo.ai/en/docs/integrations/discord) · [Google Drive](https://epismo.ai/en/docs/integrations/google-drive).
+
 ## Access and sharing
 
 Resources use a nested `access` object with `visibility` (`private` or `public`) and UUID-to-role grants (`viewer` or `editor`):

package/package.json

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