@drip-apex/apex-cli 0.15.3 → 0.16.0

package/package.json

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

package/skills/apex-cli/SKILL.md

@@ -5,6 +5,8 @@ description: Use the Apex CLI to build, inspect, QA, and hand off Apex experimen
 
 # Apex CLI
 
+If `apex` is not on the PATH, install it once with `npm install -g @drip-apex/apex-cli`, then call `apex`. Do not run `npx @drip-apex/apex-cli@latest` per command: npx contacts the npm registry before the CLI starts and hangs with no output when the registry is slow or blocked. `apex --help` and `apex schema --json` need no network.
+
 Start by asking the installed CLI for its live contract:
 
 ```bash
@@ -63,9 +65,12 @@ but a human must launch from the dashboard approval surface.
 - `3`: validation
 - `4`: confirmation required; inspect `error.details.retry`
 - `5`: conflict
+- `6`: a check command reported a definite failing verdict
 
 ## Headless Behavior
 
+Every JSON envelope may carry update and warnings. If update.required is true, or a warning has code cli_upgrade_required, first check whether the command succeeded (ok is true). If it succeeded, do not rerun it: run apex upgrade (or the command in update.command) before any further work. If it failed with the upgrade-required error (code cli_upgrade_required), run apex upgrade, then rerun the same command. Tell your user you upgraded. If only cli_update_available is present, finish the current task, then upgrade before the next one.
+
 Do not wait for prompts in CI or agent runs. If a command returns exit `4`,
 rerun with the exact flag named in the JSON error details only after checking
 the plan or destructive action.
@@ -107,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