myte 0.0.6 → 0.0.8

package/README.md

@@ -11,17 +11,29 @@ Use one of these flows:
   - then run `npx myte config --json`
   - then run `npx myte bootstrap`
   - then run `npx myte sync-qaqc`
+  - then run `npx myte feedback-sync`
   - 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-owner --subject "QAQC progress" --body-file ./updates/owner.md`
+  - 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 feedback-sync`
   - 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-owner --subject "QAQC progress" --body-file ./updates/owner.md`
+  - 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 feedback-sync`
   - `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-owner --subject "QAQC progress" --body-file ./updates/owner.md`
+  - `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.
 
@@ -112,6 +124,32 @@ Useful forms:
 - `npx myte sync-qaqc --dry-run --json`
 - `npx myte sync-qaqc --output-dir ./MyteCommandCenter`
 
+## Sync open feedback and PRD context
+
+Run this from the wrapper root that contains the project's repo folders:
+
+- `npx myte feedback-sync`
+- or `npm exec myte -- feedback-sync`
+- or `myte feedback-sync`
+
+What it does:
+- fetches a project-scoped feedback snapshot from the API using your project key
+- defaults to open `Pending` feedback
+- writes feedback cards under `MyteCommandCenter/data/feedback/items`
+- writes readable PRD markdown copies under `MyteCommandCenter/data/feedback/prds` when available
+- fully replaces the feedback-owned sync folders so stale feedback does not accumulate locally
+
+Files written:
+- `MyteCommandCenter/data/project.yml`
+- `MyteCommandCenter/data/feedback/manifest.json`
+- `MyteCommandCenter/data/feedback/items/<feedback_id>.yml`
+- `MyteCommandCenter/data/feedback/prds/<feedback_id>.md` when PRD text exists
+
+Useful forms:
+- `npx myte feedback-sync --json`
+- `npx myte feedback-sync --dry-run --json`
+- `npx myte feedback-sync --status Pending --source User`
+
 ## Query with deterministic diff context
 
 Example:
@@ -188,11 +226,79 @@ 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`
+
+## Owner updates
+
+Use `update-owner` to send a direct project-owner email through the project-key Project Assistant surface.
+
+Examples:
+
+- `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
+- `npx myte update-owner --subject "Board cleanup needed" --body-markdown "## Status\n- Phase 2 review pending"`
+- `Get-Content -Raw .\updates\owner.md | npx myte update-owner --stdin --subject "Owner update"`
+
+What it sends:
+
+- `POST /api/project-assistant/update-owner`
+- payload: `{ "subject": "...", "body_markdown": "..." }`
+
+Notes:
+
+- the owner recipient is resolved from the authenticated project
+- the CLI cannot set an arbitrary recipient address
+- the backend sends the email through Myte SMTP and stores a durable send record
+
+## 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 feedback-sync`
 - `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-owner --subject "QAQC progress" --body-file ./updates/owner.md`
+- `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.6",
+  "version": "0.0.8",
   "description": "Myte developer CLI (Project Assistant + deterministic diffs).",
   "type": "commonjs",
   "license": "MIT",
@@ -16,6 +16,6 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.6"
+    "@mytegroupinc/myte-core": "0.0.8"
   }
 }