exponential-cli 1.8.0 → 1.10.0

package/README.md

@@ -70,9 +70,17 @@ exponential actions create -n "Task name" -d "Description" -p <project-id> --pri
 exponential actions update --id <action-id> --kanban DONE
 exponential actions update --id <action-id> -n "New name" --priority "2nd Priority" --due 2026-03-15
 
-# Get today's actions
+# Set the do-date (when you plan to work on it). This is what `today` partitions on,
+# and it takes precedence over --due.
+exponential actions update --id <action-id> --scheduled-start 2026-08-05T09:00
+exponential actions update --id <action-id> --scheduled-start null   # clear it
+
+# What's actually on your plate: overdue + today + inbox
 exponential actions today
 
+# Just the actions whose dueDate is today (excludes overdue — see note below)
+exponential actions today --due-only
+
 # Get actions in a date range
 exponential actions range --start 2024-01-01 --end 2024-01-31
 
@@ -80,6 +88,48 @@ exponential actions range --start 2024-01-01 --end 2024-01-31
 exponential actions kanban --project <project-id>
 ```
 
+#### Triaging an overdue pile
+
+A large overdue count is usually not a large number of missed commitments — it's
+a few bulk writes (a generated project plan, an import) that stamped every row
+with one identical timestamp. `actions overdue` separates the two:
+
+```bash
+exponential actions overdue
+```
+
+```
+Overdue: 43
+
+21 of these were bulk-created — stamped with one identical timestamp,
+so almost certainly never individually due.
+
+  17 actions stamped 2026-07-25T08:29:55.483Z (10d overdue)
+    Projects: Entity Money Map, Net Worth Baseline, Tax Reserve System, …
+    Amnesty: exponential actions defer --ids cmqcgvtlh…,cmqcgvtnn…,…
+
+19 individually dated — real debt, oldest first.
+   12d  Send out the job description for the data engineering role [Hiring]
+```
+
+Then pick a disposition:
+
+```bash
+# Amnesty: clear the dates, back to the project backlog untimed.
+# For work that was never really due on the date it carries.
+exponential actions defer --ids id1,id2,id3
+
+# Reschedule: still due, just later.
+exponential actions reschedule --ids id1,id2 --to today
+exponential actions reschedule --ids id1,id2 --to 2026-08-10
+```
+
+> **Note on `actions today`:** as of v1.9.0 this returns the same
+> overdue/today/inbox partition the `/today` page renders, rather than a
+> due-date-only list. The old behaviour silently omitted the overdue pile — it
+> would report 6 actions while 43 sat overdue. Pass `--due-only` for the
+> previous output shape.
+
 ### Projects
 
 ```bash
@@ -98,8 +148,38 @@ exponential workspaces list
 
 # Set default workspace
 exponential workspaces set-default <workspace-slug>
+
+# List members — each row carries the mention markup for that person
+exponential workspaces members --search andi
 ```
 
+### Comments and @mentions
+
+Features, tickets, actions, pages, and goals all take comments:
+
+```bash
+exponential features comment list --feature <feature-id>
+exponential features comment add  --feature <feature-id> -m "Looks good to me"
+exponential tickets  comment add  --id <ticket-id>       -m "Reproduced on staging"
+exponential pages    comment add  --page <page-id>       -m "Needs a diagram"
+exponential goals    comment add  --goal 42              -m "On track for Q3"
+```
+
+A mention is the literal markup `@[Display Name](userId)` — writing plain `@andi`
+notifies nobody. `--mention` expands a name, email, or user id into that markup:
+
+```bash
+exponential features comment add --feature <feature-id> \
+  --mention andi \
+  -m "@andi — could you sanity-check the scope here?"
+```
+
+`@andi` is substituted in place so the sentence still reads. If the body has no
+matching `@handle` the mention is prepended instead. `--mention` is repeatable,
+and an ambiguous name is an error rather than a guess.
+
+Editing and deleting are author-only. Find ids with `exponential search "<text>"`.
+
 ## Output Formats
 
 ### JSON Output (for LLMs and automation)