@drip-apex/apex-cli 0.16.0 → 0.17.0

package/README.md

@@ -191,7 +191,9 @@ including every subcommand, argument, option, and alias.
 - `apex simulate` — simulate data-layer triggers without emitting events.
 - `apex experiments status [folder-or-id]` — read context, file versions, QA, and handover next steps without writing. Defaults to the current pulled folder.
 - `apex experiments` — create, inspect, operate, and synchronize experiments.
+- `apex results` — inspect, preview, and import historical CSV or JSON test results.
   Use `apex experiments screenshots <id-or-slug>` to force-assign every capture, including control, to its variation server-side for deterministic screenshots. Resume a job that outlives the CLI timeout with `--job <id>`; polling continues without creating another job, and the stored job's devices and variations win, so `--devices`/`--variations` are ignored (the CLI warns). The command attaches terminal jobs to the QA run by default; use `--no-attach-qa` to opt out. Choose devices with `--devices`, filter treatments with `--variations`, and use `--json` for the signed result payload. Use `apex experiments qa evidence` with `--job`, repeatable `--file`, or `--records` to write QA evidence directly.
+- `apex commerce` — look up Shopify products, live prices and costs for commerce drafts.
 - `apex push` — synchronize `.drip.config.ts` with Apex.
 - `apex preview` — open a variation QA preview; `--proxy` returns a `qa_run` receipt. Its `automated_evidence_count` counts the normalized `evidenceRecords` across all evidence kinds, matching the list shown by `apex experiments qa status`.
 - `apex roadmap` — consume approved roadmap ideas and handoffs.
@@ -238,6 +240,9 @@ command inventory:
 | `apex admin customers create` | Create internal, demo or dogfood accounts with a platform user key. Requires `--name`, `--category`, an 8 to 500 character `--reason`, and `--confirm`. |
 | `apex admin shops archive <shopId>` | Archive a shop and disable Apex delivery; use `--force` in non-interactive environments. |
 | `apex admin shops restore <shopId>` | Restore an archived shop while leaving its runtime kill switch unchanged. |
+| `apex admin shops settings list --shop <uuid-or-domain>` | Read every registered per-shop setting, value, override and group with a platform user API key. |
+| `apex admin shops settings get --shop <uuid-or-domain> --key <key>` | Read one setting; unknown keys list the available registry keys. |
+| `apex admin shops settings set --shop <uuid-or-domain> --key <key> --value <value>` | Resolve and pin the shop, then make an audited write. Booleans accept on/off/true/false; numbers must be finite; null clears nullable settings. Sensitive writes require `--confirm`; optional `--reason` and `--expected-version` preserve audit context and concurrency. |
 
 ## Landing pages built outside Apex
 
@@ -578,3 +583,7 @@ or `--claim-shop <UUID>`, exclusively. `woo` maps to `woocommerce` and `other` t
 `custom`. `--owner <email>` sends an owner invitation and requires a store;
 accounts without a store have no invitations. Output includes the organization ID,
 store ID (or null), invitation results and partial delivery status.
+
+## Import past results
+
+Upload CSV or JSON exports with `apex results import --file results.csv --dry-run`. Apex suggests column and outcome-value mappings from the file; use repeated `--map 'Column=field'` and `--outcome-value 'Source value=won|lost|inconclusive'` overrides, then pass `--yes` for non-interactive confirmation. Files are inspected and previewed before any rows are written. `--source <name>` applies to the confirmed rows; the preview shows the uploaded file name.