myte 0.0.5 → 0.0.7

package/README.md

@@ -10,15 +10,24 @@ Use one of these flows:
   - `npm install myte`
   - then run `npx myte config --json`
   - then run `npx myte bootstrap`
+  - then run `npx myte sync-qaqc`
   - then run `npx myte query "What changed in logging?" --with-diff`
+  - then run `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
+  - then run `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
   - or `npm exec myte -- query "What changed in logging?" --with-diff`
 - Global install:
   - `npm i -g myte`
   - then run `myte bootstrap`
+  - then run `myte sync-qaqc`
   - then run `myte query "What changed in logging?" --with-diff`
+  - then run `myte update-team "Backend deploy completed; QAQC rerun queued."`
+  - then run `myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
 - No install:
   - `npx myte@latest bootstrap`
+  - `npx myte@latest sync-qaqc`
   - `npx myte@latest query "What changed in logging?" --with-diff`
+  - `npx myte@latest update-team "Backend deploy completed; QAQC rerun queued."`
+  - `npx myte@latest update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
 
 `npm install myte` by itself does not put `myte` on your shell PATH. Use `npx myte` or `npm exec myte -- ...` unless you installed globally.
 
@@ -65,6 +74,8 @@ What it does:
 - fetches a project-scoped bootstrap snapshot from the API using your project key
 - validates the current wrapper workspace against the configured repo names
 - writes local files under `MyteCommandCenter/data`
+- writes a normalized public Command Center schema, not raw backend mission/proposal documents
+- excludes internal fields like `_id`, `org_id`, `project_id`, `created_by`, `assigned_to`, and raw `qa_qc_results`
 
 Files written:
 - `MyteCommandCenter/data/project.yml`
@@ -79,6 +90,34 @@ Useful forms:
 - `npx myte bootstrap --dry-run --json`
 - `npx myte bootstrap --output-dir ./MyteCommandCenter`
 
+## Sync active mission QAQC context
+
+Run this from the wrapper root that contains the project's repo folders:
+
+- `npx myte sync-qaqc`
+- or `npm exec myte -- sync-qaqc`
+- or `myte sync-qaqc`
+
+What it does:
+- fetches a project-scoped QAQC sync snapshot from the API using your project key
+- works even if `bootstrap` has not been run yet
+- creates `MyteCommandCenter/data/qaqc` automatically if it does not exist
+- syncs only active `Todo` and `In Progress` missions
+- writes a public QAQC summary per mission, not raw `qa_qc_results` or raw batch docs
+- removes previously QAQC-managed mission files from `MyteCommandCenter/data/missions` when they are no longer active
+
+Files written:
+- `MyteCommandCenter/data/project.yml`
+- `MyteCommandCenter/data/missions/<mission_id>.yml` for active missions
+- `MyteCommandCenter/data/qaqc/active-missions/<mission_id>.yml`
+- `MyteCommandCenter/data/qaqc/manifest.json`
+- `MyteCommandCenter/data/qaqc/latest-batch.json`
+
+Useful forms:
+- `npx myte sync-qaqc --json`
+- `npx myte sync-qaqc --dry-run --json`
+- `npx myte sync-qaqc --output-dir ./MyteCommandCenter`
+
 ## Query with deterministic diff context
 
 Example:
@@ -155,10 +194,56 @@ To inspect the exact payload before sending it:
 - `npx myte create-prd ./drafts/auth-prd.md --print-context`
 - `npx myte create-prd ./drafts/auth-prd.md --description "Short card summary" --print-context`
 
+## Team updates
+
+Use `update-team` to add a project comment through the project-key Project Assistant surface.
+
+Examples:
+
+- `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
+- `npm exec myte -- update-team "Frontend review is ready for sign-off."`
+- `Get-Content -Raw .\notes\team-update.md | npx myte update-team --stdin`
+
+What it sends:
+
+- `POST /api/project-assistant/project-comment`
+- payload: `{ "content": "..." }`
+
+Useful forms:
+
+- `npx myte update-team "Backend deploy completed." --print-context`
+- `npx myte update-team "Backend deploy completed." --json`
+
+## Client update drafts
+
+Use `update-client` to draft a branded client update email for owner review.
+
+Examples:
+
+- `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
+- `npx myte update-client --subject "Weekly client update" --body-markdown "## Progress\n- Login complete" --target-contact-ids 507f1f77bcf86cd799439011,507f1f77bcf86cd799439012`
+- `Get-Content -Raw .\updates\week-12.md | npx myte update-client --stdin --subject "Weekly client update"`
+
+What it sends:
+
+- `POST /api/project-assistant/client-update-drafts`
+- payload: `{ "subject": "...", "body_markdown": "...", "target_contact_ids": ["..."] }`
+
+Notes:
+
+- `--subject` is required.
+- The body can come from `--body-markdown`, `--body-file`, a positional file path, positional inline text, or `--stdin`.
+- `target_contact_ids` are optional. If omitted, the backend selects the linked primary client contact when available.
+- Use `--target-contact-id <id>` multiple times or `--target-contact-ids <id1,id2>`.
+- The CLI prints the returned draft summary, including the draft id, status, recipients, and snippet.
+
 ## Common commands
 
 - `npm install myte`
 - `npx myte bootstrap`
+- `npx myte sync-qaqc`
 - `npx myte config --json`
 - `npx myte query "Summarize the current branch changes" --with-diff`
 - `npx myte create-prd ./drafts/auth-prd.md`
+- `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
+- `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "myte",
-  "version": "0.0.5",
+  "version": "0.0.7",
   "description": "Myte developer CLI (Project Assistant + deterministic diffs).",
   "type": "commonjs",
   "license": "MIT",
@@ -16,6 +16,6 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.5"
+    "@mytegroupinc/myte-core": "0.0.7"
   }
 }