@drip-apex/apex-cli 0.15.3 → 0.15.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/AGENTS.md +16 -10
  2. package/README.md +45 -23
  3. package/dist/cli.js +1363 -347
  4. package/package.json +1 -1
  5. package/skills/apex-cli/SKILL.md +5 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@drip-apex/apex-cli",
3
- "version": "0.15.3",
3
+ "version": "0.15.4",
4
4
  "license": "MIT",
5
5
  "description": "Apex CLI for managing experiments, approved roadmap ideas, and draft workspaces.",
6
6
  "private": false,
package/skills/apex-cli/SKILL.md CHANGED
@@ -5,6 +5,8 @@ description: Use the Apex CLI to build, inspect, QA, and hand off Apex experimen
5
5
 
6
6
  # Apex CLI
7
7
 
8
+ 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.
9
+
8
10
  Start by asking the installed CLI for its live contract:
9
11
 
10
12
  ```bash
@@ -63,9 +65,12 @@ but a human must launch from the dashboard approval surface.
63
65
  - `3`: validation
64
66
  - `4`: confirmation required; inspect `error.details.retry`
65
67
  - `5`: conflict
68
+ - `6`: a check command reported a definite failing verdict
66
69
 
67
70
  ## Headless Behavior
68
71
 
72
+ 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.
73
+
69
74
  Do not wait for prompts in CI or agent runs. If a command returns exit `4`,
70
75
  rerun with the exact flag named in the JSON error details only after checking
71
76
  the plan or destructive action.