@zalify/cli 0.18.0 → 0.20.0
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.
- package/README.md +8 -0
- package/dist/cli.js +7308 -18
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -101,7 +101,15 @@ its new home under `shop`.
|
|
|
101
101
|
| --- | --- |
|
|
102
102
|
| `ads create <dir>` | Provision an Autopilot brand-instance GitHub repo (POST `/api/repos`, GitHub App), scaffold the starter locally (`identity.yaml`, `brand.yaml`, `policy/`, `campaigns/`, `media-plans/`, `signals/`, `decisions/`), and push with a short-lived repo-scoped token. Writes `.zalify/brand-repo.json` so later commands run arg-free. The directory name becomes the slug — use the workspace's store slug so the service's digest writer can find the repo |
|
|
103
103
|
| `ads` / `ads list` | List the workspace's brand instances and their provisioning status |
|
|
104
|
+
| `ads new <name> [--objective] [--budget] [--country] [--link]` | Scaffold a campaign FOLDER — the drag-and-drop form: `campaign.yaml` for budget/audience/copy defaults, `creatives/` for the files that become ads. Three questions when interactive, flags otherwise. `cp -r` an existing folder to duplicate a campaign |
|
|
104
105
|
| `ads remove <slug>` | Deprecate a brand instance — soft-deletes the record (drops out of `ads list` and the service's repo-token minting; survives for history). The GitHub repo is deliberately untouched: deleting real campaign intent is a human-on-GitHub decision |
|
|
106
|
+
| `ads status` | The instance at a glance: brand + consent, platform access and credential expiry, ingestion freshness (with per-account failures), first-party join coverage, plan and pending-proposal counts. Exits non-zero when the service reports problems |
|
|
107
|
+
| `ads report [--date <YYYY-MM-DD>] [--platform <all\|meta\|google>]` | The daily report in the terminal — totals vs the day before, where the money moved, what changed in the account |
|
|
108
|
+
| `ads digest [dir]` | Print the repo's `signals/latest.json` — the curated numbers the service writes daily and agents draft against. Reads the LOCAL checkout |
|
|
109
|
+
| `ads plan` / `ads plan list` | Media plans recorded by the service, newest first |
|
|
110
|
+
| `ads plan show <id>` | One plan's content (by id, or `slug@version`) |
|
|
111
|
+
| `ads open` | Open the Structure canvas for the active workspace |
|
|
112
|
+
| `ads doctor [dir]` | Checks that have each broken once: checkout↔record link, workspace match, **slug alignment** (service brand vs repo record — misalignment silently kills digest writes), consent drift, brand-vs-account timezone match, credential expiry and degradation |
|
|
105
113
|
|
|
106
114
|
The engine commands — `plan` / `apply` / `creative` / `report` — join this
|
|
107
115
|
group as `@zalify/ads-engine` merges in. Until then, drafting and applying
|