myte 0.0.12 → 0.0.14

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 (2) hide show
  1. package/README.md +7 -5
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -116,22 +116,23 @@ Useful forms:
116
116
 
117
117
  Run this from any workspace with a valid project key:
118
118
 
119
- - `npx myte run-qaqc --mission-ids M001,M002 --wait --sync`
120
- - or `npm exec myte -- run-qaqc --mission-ids M001,M002 --wait --sync`
121
- - or `myte run-qaqc --mission-ids M001,M002 --wait --sync`
119
+ - `npx myte run-qaqc --mission-ids "M001,M002" --wait --sync`
120
+ - or `npm exec myte -- run-qaqc --mission-ids "M001,M002" --wait --sync`
121
+ - or `myte run-qaqc --mission-ids "M001,M002" --wait --sync`
122
122
 
123
123
  What it does:
124
124
  - queues QAQC for up to 10 explicit mission ids through the project-key API surface
125
125
  - returns a `batch_id` immediately
126
126
  - uses `--wait` to poll the batch until it reaches a terminal state
127
127
  - uses `--sync` to refresh `MyteCommandCenter/data/qaqc.yml` after a completed batch
128
+ - on PowerShell, quote comma-separated multi-id values: `--mission-ids "M001,M002"`
128
129
  - runs through the dedicated `project_api_qaqc` queue inside the existing Celery service, with a global budget of `20` dispatch starts/minute and `20` live jobs
129
130
  - a saturated `run-qaqc --wait` batch can take roughly `5-10` minutes before sync has final data to pull
130
131
 
131
132
  Useful forms:
132
133
  - `npx myte run-qaqc --mission-ids M001`
133
- - `npx myte run-qaqc --mission-ids M001,M002 --wait`
134
- - `npx myte run-qaqc --mission-ids M001,M002 --wait --sync --json`
134
+ - `npx myte run-qaqc --mission-ids "M001,M002" --wait`
135
+ - `npx myte run-qaqc --mission-ids "M001,M002" --wait --sync --json`
135
136
 
136
137
  ## Sync active mission QAQC context
137
138
 
@@ -365,6 +366,7 @@ Notes:
365
366
  - `--subject` is required.
366
367
  - The body can come from `--body-markdown`, `--body-file`, a positional file path, positional inline text, or `--stdin`.
367
368
  - `target_contact_ids` are optional. If omitted, the backend selects the linked primary client contact when available.
369
+ - If no linked client contacts exist, the backend falls back to the project owner so internal projects can still draft/send updates through the same flow.
368
370
  - Use `--target-contact-id <id>` multiple times or `--target-contact-ids <id1,id2>`.
369
371
  - The CLI prints the returned draft summary, including the draft id, status, recipients, and snippet.
370
372
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "myte",
3
- "version": "0.0.12",
3
+ "version": "0.0.14",
4
4
  "description": "Myte developer CLI (Project Assistant + deterministic diffs).",
5
5
  "type": "commonjs",
6
6
  "license": "MIT",
@@ -16,6 +16,6 @@
16
16
  "node": ">=18"
17
17
  },
18
18
  "dependencies": {
19
- "@mytegroupinc/myte-core": "0.0.12"
19
+ "@mytegroupinc/myte-core": "0.0.14"
20
20
  }
21
21
  }