@drip-apex/apex-cli 0.6.1 → 0.6.2

package/AGENTS.md

@@ -54,6 +54,15 @@ the first writes: `apex experiments create`, `apex goals create`,
 - Stale workspace or filesystem: pull fresh files, reapply your edits, and plan again.
 - Server limit errors: read the JSON error details; Apex includes server-owned limits when available.
 
+## Platform Shop Administration
+
+- `apex admin shops archive <shopId>` archives a shop; headless callers must
+  inspect exit `4` and rerun the supplied `--force` command only when intended.
+- `apex admin shops restore <shopId>` restores an archived shop. Restoration
+  does not re-enable delivery; the runtime kill switch remains authoritative.
+- Both commands require a platform user API key. Organization and shop keys
+  are intentionally insufficient.
+
 ## Filesystem Rules
 
 - Formatting is enforced by Biome (`npm run format`); do not hand-wrap code.

package/README.md

@@ -72,6 +72,8 @@ apex experiments pull <id-or-slug> --out ./my-test
 apex experiments plan ./my-test --json
 apex experiments apply ./my-test --json
 apex experiments qa status ./my-test --json
+apex experiments qa evidence ./my-test --file ./desktop.png --device desktop
+apex experiments qa evidence <id-or-slug> --job <screenshot-job-id>
 apex experiments screenshots <id-or-slug> --out ./screenshots
 
 apex workspace checkout <experimentId> --variation <variationId> --out ./workspace
@@ -121,7 +123,7 @@ including every subcommand, argument, option, and alias.
 - `apex webhooks` — manage shop webhooks.
 - `apex simulate` — simulate data-layer triggers without emitting events.
 - `apex experiments` — create, inspect, operate, and synchronize experiments.
-  Use `apex experiments screenshots <id-or-slug>` to force-assign every capture, including control, to its variation server-side for deterministic screenshots; choose devices with `--devices`, filter treatments with `--variations`, and use `--json` for the signed result payload.
+  Use `apex experiments screenshots <id-or-slug>` to force-assign every capture, including control, to its variation server-side for deterministic screenshots. 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 push` — synchronize `.drip.config.ts` with Apex.
 - `apex preview` — open a variation QA preview.
 - `apex roadmap` — consume approved roadmap ideas and handoffs.
@@ -156,6 +158,14 @@ including every subcommand, argument, option, and alias.
 - `apex schema` — emit the machine-readable CLI schema.
 - `apex discover` — read observed tracking shapes or mine a public GTM container.
 
+Platform-administrator shop commands are intentionally outside the public
+command inventory:
+
+| Command | Purpose |
+| --- | --- |
+| `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. |
+
 ## Which local format am I in?
 
 Inspect the marker under `.apex/`: `experiment-filesystem.json` means the