@samva/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.
Files changed (4) hide show
  1. package/AGENTS.md +8 -0
  2. package/README.md +3 -3
  3. package/dist/bin.mjs +3771 -2921
  4. package/package.json +12 -12
package/AGENTS.md CHANGED
@@ -79,6 +79,14 @@ uploads again. `--dry-run` lists each attachment and uploads nothing.
79
79
  or the newest publication that still validates input identically. They are mutually exclusive and
80
80
  each requires `--template-id`, because a reference is a statement about one template's history.
81
81
 
82
+ `samva templates list --shared true|false` filters by whether the template's project is shared with
83
+ every namespace, and every listed template reports `shared`. Sharing belongs to an organization-level
84
+ project: `templates create --shared` shares the new project and refuses a namespace (exit `2`), and
85
+ `templates update <id> --data '{}' --shared true|false` shares or unshares the project for every
86
+ entry in it. `--shared` that disagrees with `shared` in `--data` exits `2`. A namespace-scoped key
87
+ lists, reads, and sends shared templates but gets 403 changing them, and the API refuses moving a
88
+ shared project into a namespace.
89
+
82
90
  `samva templates workspace <open|diff|patch|add-asset|check|fixture|save|history|publish>` is the
83
91
  hosted project workspace over the CLI, for a caller with no clone: an agent in a sandbox, a CI job,
84
92
  a script. It reaches the same operations the hosted MCP tools reach, so an agent can start a journey in one
package/README.md CHANGED
@@ -184,12 +184,12 @@ default-exports `defineTemplate` with an input schema, declared fixtures, and an
184
184
  `whatsapp` body. The compiler reads the file without running it, so top-level code in a template
185
185
  does not execute. `check` type-checks the project, compiles every template, and renders every
186
186
  fixture through every channel the template declares; `build` writes those rendered fixtures, each
187
- template's input schema, and its compiled IR. Modules without a template default export are
187
+ template's input schema, and its compiled template. Modules without a template default export are
188
188
  helpers, and every template needs a unique id.
189
189
 
190
- The JSON file written by `build` uses `schemaVersion: 3`. Its `result` is the `@samva/vite/build`
190
+ The JSON file written by `build` uses `schemaVersion: 4`. Its `result` is the `@samva/vite/build`
191
191
  result: `files[]`, one per template entry, each with `ok`, `diagnostics`, and a `template` carrying
192
- `template` (the id), `channels`, `source`, `inputSchema`, `ir`, `fixtures[]` (each with its `email`
192
+ `template` (the id), `channels`, `source`, `inputSchema`, `compiled`, `fixtures[]` (each with its `email`
193
193
  subject, preheader, HTML and text, its `sms` text, or its `whatsapp` message), and `compatibility`
194
194
  findings. The former `preview.kind` `"email"` and `"structured"` shapes no longer exist. The CLI's
195
195
  stdout envelope remains version 1.