@drip-apex/apex-cli 0.6.3 → 0.8.0

package/package.json

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

package/skills/apex-cli/SKILL.md

@@ -13,7 +13,6 @@ apex schema --json
 
 Prefer JSON output. When stdout is piped, Apex emits JSON by default.
 
-
 ## Zero-Experiment Shop Bootstrap
 
 CLI-only bootstrap is supported for a fresh shop before any experiments exist.
@@ -64,7 +63,6 @@ Platform administrators can archive a mistakenly created shop with
 stop those tests rather than retrying or overriding the refusal. Restore leaves
 delivery controlled by the runtime kill switch.
 
-
 ## Project code
 
 ```sh
@@ -91,3 +89,14 @@ A successful write returns `saved`, its diff, backup path, current version, writ
 and precompile result. A failed precompile is a saved-write warning. All warnings remain
 in JSON and are also written to stderr. User keys resolve domains or pin UUID context;
 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.
+
+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
+whether a full refresh succeeded. Server-owned QA and launch files are healed.
+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.