@drip-apex/apex-cli 0.14.2 → 0.15.1

package/README.md

@@ -177,7 +177,7 @@ including every subcommand, argument, option, and alias.
 - `apex triggers apply-recipe` — apply a server-owned trigger recipe.
 - `apex triggers enable-capture` — enable temporary setup capture.
 - `apex triggers disable-capture` — disable setup capture and clear its expiry.
-- `apex domains` — manage install domains.
+- `apex domains` — manage install domains, and landing-page domains (`claim`, `register`, `status`, `unclaim`; registering asks for a price confirmation).
 - `apex handover` — manage cross-domain identity handover.
 - `apex install` — generate storefront installation snippets.
 - `apex funnels` — manage analytics funnels.
@@ -215,7 +215,7 @@ including every subcommand, argument, option, and alias.
 
 - `apex external-pixels` — manage external pixel snippets.
 - `apex assets` — manage uploaded assets.
-- `apex landing-pages` — discover landing pages.
+- `apex landing-pages` — build landing pages with your own tools, then apply, preview, deploy and roll them back.
 - `apex brand` — manage brand context.
 - `apex shops` — manage shops and active-shop context.
 - `apex skills` — inspect agent skill guidance.
@@ -227,13 +227,52 @@ command inventory:
 
 | Command | Purpose |
 | --- | --- |
+| `apex admin customers create` | Create internal, demo or dogfood accounts with a platform user key. Requires `--name`, `--category`, an 8 to 500 character `--reason`, and `--confirm`. |
 | `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. |
 
+## Landing pages built outside Apex
+
+A landing page is built in a checkout folder by any tool (Claude Code, Codex,
+a static-site build); Apex keeps its versions, goals and deploys.
+
+```bash
+apex landing-pages create --name "Fall sale" --out ./fall-sale   # or: pull <id> --out ./fall-sale
+# edit ./fall-sale/index.html and its assets; context/ holds brand, catalog, offers and reviews
+apex landing-pages plan ./fall-sale             # what would change
+apex landing-pages apply ./fall-sale --yes      # new version + signed preview link (24 hours)
+apex landing-pages deploy ./fall-sale           # live on <shop>.apex-page.com, or the host in apex-landing-page.json
+apex landing-pages rollback ./fall-sale --version 1
+apex landing-pages experiment ./fall-sale --control 1 --variant 2   # draft split; start it in the dashboard
+```
+
+The folder holds the page files (index.html at the root, at most 300 files
+and 100 MB; html, css, js, json, svg, images, fonts, txt, xml, webmanifest, mp4 and webm),
+`apex-landing-page.json` and the `context/` folder (each pull replaces its JSON
+files with the server's current set). Build with relative asset
+URLs (Vite `base: "./"`). `apex-landing-page.json` sets the name, slug, an
+optional `host`, a domain claimed with `apex domains claim <host>` (without
+one, or `--host`, a deploy goes to the shop's own instant host
+`<shop>.apex-page.com`), the `path` (default `/<slug>`), whether Apex injects the shop snippet
+(`snippet`, on by default), the `shop_hosts` that receive the visitor's identity
+on outbound links (default: the shop's install domains), the `goals`
+(key, name, type click, pageview or custom) and an optional `experiment`
+(control and variant version numbers). Apply refuses to run without `--yes`
+when no terminal can confirm, and refuses with exit 5 when the page changed
+since the pull (`--force` replaces it anyway). Pull refuses to overwrite a
+checkout with changes that are not applied, or a folder's own files that are not a
+checkout (exit 5; `--force` discards or replaces them). A deploy makes the page's goals match
+`apex-landing-page.json`, so a goal edited in the dashboard is reset. A deploy or rollback while an
+experiment splits the page keeps serving the experiment's two arms and
+leaves its goals as they are (new manifest goals are added); the deployed
+version serves when the experiment ends, and its goal changes apply at the
+next deploy after that.
+
 ## Which local format am I in?
 
 Inspect the marker under `.apex/`: `experiment-filesystem.json` means the
-folder belongs to `apex experiments pull/plan/apply`, while `session.json`
+folder belongs to `apex experiments pull/plan/apply`, `landing-page.json` means
+an `apex landing-pages` checkout, while `session.json`
 means it is an `apex workspace checkout/status/publish` workspace. Keep the two
 formats in different folders; when the wrong command is run, Apex points to the
 matching status command.
@@ -485,3 +524,30 @@ are sent. Login/logout, tests, the mock transport, and runs with no resolvable c
 (`APEX_API_KEY` or `DRIP_API_KEY`) are recorded with credential kind `env` unless
 `APEX_TELEMETRY=0`. Set `APEX_TELEMETRY=0` to disable the beacon. The best-effort request has an
 800 ms timeout and never changes command output or exit status.
+
+MP4 (`video/mp4`) and WebM (`video/webm`) videos are hosted directly by Apex.
+Each version holds at most 300 files and 100 MB; each video is limited to 50 MB,
+and other files to 3 MB. `apply` automatically obtains a 15-minute upload grant
+for videos above 3 MB and sends resumable 8 MB parts straight to the Worker,
+retrying failed parts with progress output. The Worker verifies the declared
+size and SHA-256 before apply records the file. Pull and signed previews also
+fetch large videos directly from the Worker. Video supports byte ranges,
+including Safari's `bytes=0-1` probe; rollback preserves the older bytes.
+
+Engineering account creation uses `apex login --user` credentials with `admin:write`
+and a live platform role with onboarding write permission. Real customer accounts
+are created in **Admin, Links**.
+
+```sh
+apex admin customers create --name "Demo workspace" --category demo --reason "Workshop demo account" --confirm --json
+apex admin customers create --name "Dogfood store" --category dogfood --domain dogfood.example.com --platform woo --owner owner@example.com --reason "Engineering dogfood account" --confirm
+```
+
+`--type` defaults to `company` (`company|agency`); `--plan` defaults to
+`self_managed` (`self_managed|apex_managed|drip_managed`). Managed plans require
+`--consultant <platform_access UUID>` and `--consultant-title <text>`.
+An optional first store uses `--domain <host> --platform <shopify|shopware|woo|other>`
+or `--claim-shop <UUID>`, exclusively. `woo` maps to `woocommerce` and `other` to
+`custom`. `--owner <email>` sends an owner invitation and requires a store;
+accounts without a store have no invitations. Output includes the organization ID,
+store ID (or null), invitation results and partial delivery status.