@cowliss/cli 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Bogdan Radu
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,105 @@
+# @cowliss/cli
+
+`cow`, the command line for Cowliss. It does everything the dashboard does,
+and it is where journeys and email templates live as TypeScript in your own
+repo.
+
+## Install
+
+```sh
+npm install -D @cowliss/cli
+```
+
+Or run it without installing:
+
+```sh
+npx -y @cowliss/cli whoami
+```
+
+Node 22 and up.
+
+## Sign in
+
+```sh
+cow login
+cow whoami
+```
+
+`cow login` opens the dashboard and caches a session token. In CI, set
+`COW_DEPLOY_KEY` to a deploy key instead.
+
+## Journeys and emails as code
+
+```sh
+cow init my-messaging
+cd my-messaging
+npm install
+```
+
+You get `cow.json`, a `journeys/` folder, an `emails/` folder, and the files
+that build them. Write a journey:
+
+```ts
+import { defineJourney } from "@cowliss/cli/journeys";
+
+export default defineJourney({
+  trigger: { event: "checkout_started" },
+  purpose: "emailMarketing",
+  run: async (event, api) => {
+    const purchased = await api.waitForEvent("purchase_completed", {
+      timeout: "24h",
+    });
+    if (purchased) {
+      return;
+    }
+    await api.email.send({
+      template: "abandoned-checkout",
+      props: { checkoutUrl: event.properties.checkoutUrl },
+    });
+  },
+});
+```
+
+Then:
+
+```sh
+# run it on a virtual clock, nothing sent
+cow test abandoned-checkout --scenario scenarios/cart.json
+
+# typecheck and bundle, no API call
+cow build
+
+# publish it and make it the environment's live code
+cow deploy --env development
+
+# rebuild and redeploy on every save
+cow dev
+```
+
+Every push creates a numbered release. `cow deploy` makes one release an
+environment's current code, `cow rollback` puts the previous one back, and a
+run that has already started stays on the release it started on.
+
+## Admin, and everything else
+
+`cow users`, `cow events`, `cow apps`, `cow sources`, `cow segments`,
+`cow journeys`, `cow deliveries`, `cow domains`, `cow billing` and the rest
+read and write the same API the dashboard uses. Add `--json` for output you
+can pipe.
+
+## For agents in your editor
+
+```sh
+cow mcp
+```
+
+An MCP server over stdio, exposing the admin API as tools. Point your editor
+at `npx -y @cowliss/cli mcp`.
+
+## Docs
+
+[docs.cowliss.com](https://docs.cowliss.com)
+
+## License
+
+MIT

package/dist/guest/constants-OZrYz4I2.d.ts

@@ -0,0 +1,42 @@
+//#region ../../packages/shared/src/constants.d.ts
+/**
+ * The two fixed environments every org has (spec: Environments). An app
+ * belongs to one, so the environment of every write is the app's;
+ * profiles, identifiers, events, memberships, journey instances,
+ * deliveries, violations, quarantine, the address ledger, and idempotency
+ * keys are per environment, while the catalog, sending domains, the
+ * suppression mirror, billing, and journey code are shared. A third
+ * environment is a one-line change here plus the mirrored db enum.
+ */
+declare const ENVIRONMENTS: readonly ["development", "production"];
+type Environment = (typeof ENVIRONMENTS)[number];
+/**
+ * Fixed consent purposes for the prototype. Consent is a per-purpose map on
+ * the profile, checked at send-step execution time.
+ *
+ * The two names describe what the recipient agreed to, not the pipe it
+ * arrives on: "emails I did not ask for individually" and "my data leaving
+ * for somewhere else". Naming them after the channel (`email`, `webhook`)
+ * said nothing a recipient could consent to, and transactional mail already
+ * bypasses the email purpose, so it was only ever marketing consent.
+ */
+declare const CONSENT_PURPOSES: readonly ["emailMarketing", "dataProcessing"];
+type ConsentPurpose = (typeof CONSENT_PURPOSES)[number];
+/**
+ * The two classes of send, declared on the template rather than passed per
+ * call so the class cannot drift between two sends of the same message.
+ *
+ * Marketing is everything a journey sends on the org's behalf: it carries
+ * the RFC 8058 unsubscribe headers and runs the full gate list.
+ * Transactional is the developer's own operational mail (a receipt, an
+ * export-is-ready notice): it carries neither header and skips consent and
+ * the per-user frequency cap, because an unsubscribe link on an invoice is
+ * wrong and a receipt must not silently vanish for anyone who once left a
+ * newsletter. Suppression, the quota, the sending pause, and the from-domain
+ * check still apply to both: those bound cost and protect the shared SES
+ * account, and none of them are about what the recipient asked for.
+ */
+declare const SEND_CLASSES: readonly ["marketing", "transactional"];
+type SendClass = (typeof SEND_CLASSES)[number];
+//#endregion
+export { Environment as n, SendClass as r, ConsentPurpose as t };