@drip-apex/apex-cli 0.6.1 → 0.6.3

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.
@@ -61,3 +70,31 @@ the first writes: `apex experiments create`, `apex goals create`,
 - Edit experiment files, variation code, metrics, and targeting only through supported paths.
 - Do not bypass the variation artifact persistence path with direct API writes.
 - Keep generated evidence outside `qa.json`; attach it through QA commands.
+
+
+## Project code
+
+```sh
+apex project-code get --shop example.com --json
+apex project-code diff --file project-code.json --shop example.com --json
+apex project-code set --file project-code.json --shop example.com --backup previous-code.json --json
+```
+
+The input is a partial projectCode object, for example `{ "css": "body { color: red; }" }`.
+Supported fields are `enabled` (boolean) and `css`, `helperJs`, and `js` (strings or null).
+Each code field permits at most 20,000 characters. Omitted fields remain unchanged.
+Null or blank code clears that field. Unknown fields and empty objects are rejected.
+
+GET returns complete code, shop identity, and an opaque version. DIFF returns effective
+before/after values and changed fields without writing. SET creates a new backup file
+with complete previous code, identity, capture time, and the exact version before PATCH.
+It never replaces an existing backup. Backup failures prevent the write. An effective
+no-op returns `unchanged`, without a PATCH or backup file.
+
+The backed-up version becomes expectedVersion unchanged. A conflict returns exit 5,
+keeps the backup, and does not retry. Read the latest state and preview it before a new
+attempt with a new backup path. Authentication uses exit 2; invalid input uses exit 3.
+A successful write returns `saved`, its diff, backup path, current version, writtenVersion,
+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.

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
@@ -107,6 +109,10 @@ including every subcommand, argument, option, and alias.
 ### Experiments and delivery
 
 - `apex consent` — manage consent gating.
+- `apex project-code` — inspect and safely change shop project code.
+- `apex project-code get` — read complete code and its opaque version.
+- `apex project-code diff` — preview a partial JSON change without writing.
+- `apex project-code set` — create a backup before a version-checked write.
 - `apex triggers` — manage data-layer triggers and temporary setup capture.
 - `apex triggers get --shop <domain-or-id>` — read the identified shop's runtime triggers.
 - `apex triggers set` — replace the shop's runtime triggers from a JSON file.
@@ -121,7 +127,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 +162,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
@@ -218,3 +232,31 @@ Read the CLI reference on the docs site:
 - https://docs.drip-apex.com/cli/commands-output
 
 Maintainers: see the [CLI release runbook](../../docs/cli-releases.md).
+
+
+## Project code
+
+```sh
+apex project-code get --shop example.com --json
+apex project-code diff --file project-code.json --shop example.com --json
+apex project-code set --file project-code.json --shop example.com --backup previous-code.json --json
+```
+
+The input is a partial projectCode object, for example `{ "css": "body { color: red; }" }`.
+Supported fields are `enabled` (boolean) and `css`, `helperJs`, and `js` (strings or null).
+Each code field permits at most 20,000 characters. Omitted fields remain unchanged.
+Null or blank code clears that field. Unknown fields and empty objects are rejected.
+
+GET returns complete code, shop identity, and an opaque version. DIFF returns effective
+before/after values and changed fields without writing. SET creates a new backup file
+with complete previous code, identity, capture time, and the exact version before PATCH.
+It never replaces an existing backup. Backup failures prevent the write. An effective
+no-op returns `unchanged`, without a PATCH or backup file.
+
+The backed-up version becomes expectedVersion unchanged. A conflict returns exit 5,
+keeps the backup, and does not retry. Read the latest state and preview it before a new
+attempt with a new backup path. Authentication uses exit 2; invalid input uses exit 3.
+A successful write returns `saved`, its diff, backup path, current version, writtenVersion,
+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.