@ghostystudio/cli 0.67.0 → 0.69.0

package/README.md

@@ -66,7 +66,9 @@ ghosty channels whatsapp history <id> --integration ID [--days 7]   [--dry-run]
 ghosty channels wa import <id> --from-file F | --from-dir DIR --own-number yes|no   [--dry-run]   # personal WhatsApp session, no QR
 ghosty channels wa pair|status|pause <id>   [--phone N]
 ghosty channels wa groups ls|enable|disable|set|create <id> [group]   [--role equipo|cliente] [--wake mention|all] [--dry-run]   # personal WhatsApp groups
-ghosty boards ls|create|assign|move-cards|rm <workspace|agent> …   [--columns-from main] [--from A --to B --integration X --dry-run]
+ghosty boards ls|create|assign|move-cards|access|rm <workspace|agent> …   [--columns-from main] [--from A --to B --integration X --dry-run] [--add|--remove EMAIL --until 14d]
+ghosty spaces members ls|add|rm <workspace> [email]   [--role member|admin] [--until 2026-10-28|14d]
+ghosty access why <email> <agent-id> | --workspace W --board B
 ghosty cards ls <id>                     [--q TEXT] [--limit 20]              # recent cards on its sales board
 ghosty cards show <id> <folio|phone|id>  [--limit 20]                         # a card's thread, attachments and whether gs kept a copy
 ghosty cards archive <id>                --integration X | --column X | --before 30d   [--dry-run]
@@ -112,6 +114,16 @@ Every command has its own help with examples: `ghosty <command> --help` or `ghos
 
 Exit codes: `0` ok · `1` API error · `2` usage error · `3` not signed in.
 
+### Changes in 0.69.0
+
+- `factory runs why` puts an unmet plan criterion on top (`approved_unmet_criterion`): approved without the preview a criterion asked for, merged without preview, smoke failed on the merged commit, or a CI criterion approved with CI `none`. Each one is listed with the criterion's text and the evidence (`acceptance[]` in `--json`). A saved analysis is redone if the run had events after it.
+
+### Changes in 0.68.0
+
+- New `spaces members ls|add|rm <workspace> [email]`: a workspace's people without the Members screen (owner, admin or staff). `--role admin` lets them invite and remove; `--until 2026-10-28` or `--until 14d` gives a temporary seat that is removed automatically — for reviewer accounts (Meta, Google, Apple).
+- New `boards access <workspace> [board]`: who sees a board, and `--add` / `--remove` on its «only these people» list (`--restrict` turns a whole-workspace board into a list, `--everyone` opens it back; `--until` works here too).
+- New `access why <email> <agent-id>` (or `--workspace W --board B`): every reason someone sees an agent or a board, and when temporary access expires.
+
 ### Changes in 0.66.0
 
 - `usage --agent <id> --by visitor`: /c without an account, one row per visitor — USD, messages, page/PDF and whether they created an account — with USD per visitor and per new account.
@@ -161,7 +173,7 @@ Exit codes: `0` ok · `1` API error · `2` usage error · `3` not signed in.
 
 ### Changes in 0.56.0
 
-- `factory runs why <run> [--refresh]`: why a run got stuck or failed — category, impact, the critical step with its evidence and what to change next time (a healthy run doesn't call the model).
+- `factory runs why <run> [--refresh]`: why a run got stuck or failed — category, impact, the critical step with its evidence and what to change next time (a healthy run doesn't call the model). It first checks the approved plan's criteria against the verdict: a criterion "in the preview" approved without the preview ready comes out on top as `approved_unmet_criterion`.
 - `factory runs show --timing` lists stuck patterns (a command open 8+ min, the same command repeated, errors in a row, going back and forth, apt install in a box); `runs stats` counts runs with stuck alerts.
 
 ### Changes in 0.55.0