@drip-apex/apex-cli 0.15.4 → 0.17.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@drip-apex/apex-cli",
-  "version": "0.15.4",
+  "version": "0.17.0",
   "license": "MIT",
   "description": "Apex CLI for managing experiments, approved roadmap ideas, and draft workspaces.",
   "private": false,

package/skills/apex-cli/SKILL.md

@@ -112,6 +112,8 @@ shop keys must match the requested identity before any backup or write.
 
 Experiment references accept an ID, slug, or test key (for example `BIO-085`). Test keys resolve within the selected shop; use `--shop <shop-id>` to change it. Bare lowercase references remain slugs.
 
+Commerce drafts live in typed `commerce/<kind>.json` files. Define each lever once, include every variation arm, and leave `serverOwned` unchanged.
+
 Filesystem apply preserves authored local bytes by default. Use
 `apex experiments apply <folder> --sync` to refresh them from stored server bytes.
 The receipt's `files` contains SHA-256 digests for every pull path; `synced` reports
@@ -120,3 +122,9 @@ Create/get return `dashboard_url`; apply returns `dashboardUrl`. These links
 switch the signed-in dashboard user's active shop before opening the experiment.
 
 Filesystem apply caches uploaded asset URLs by byte SHA-256 in `.apex/experiment-filesystem.json`, so unchanged images reuse their URL across applies without rewriting authored files.
+
+Per-shop settings use a platform user API key: `apex admin shops settings list --shop <uuid-or-domain>`, `get --shop <uuid-or-domain> --key <key>`, or `set --shop <uuid-or-domain> --key <key> --value <value>`. The CLI resolves domains through GET and pins writes to the returned UUID. If a domain is ambiguous, use one of the candidate UUIDs. Boolean values accept on/off/true/false, numbers must be finite, enum/string values are text, and null clears nullable settings. Add `--reason` for audit context and `--expected-version` for concurrency. Sensitive writes require `--confirm`; exit 4 provides the exact rerun command. Prefer `--json` to read the response envelope. The registry owns permissions and write paths, so settings with another owner may refuse this write.
+
+## Import past results
+
+Run `apex results import --file <csv-or-json> --dry-run` first. Resolve missing fields with `--map 'Column=title|outcome|learning'` and source verdicts with `--outcome-value 'Value=won|lost|inconclusive'`. Review the preview, then rerun with `--yes` in non-interactive environments.