myte 0.0.7 → 0.0.8

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 +55 -0
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -11,22 +11,28 @@ Use one of these flows:
11
11
  - then run `npx myte config --json`
12
12
  - then run `npx myte bootstrap`
13
13
  - then run `npx myte sync-qaqc`
14
+ - then run `npx myte feedback-sync`
14
15
  - then run `npx myte query "What changed in logging?" --with-diff`
15
16
  - then run `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
17
+ - then run `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
16
18
  - then run `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
17
19
  - or `npm exec myte -- query "What changed in logging?" --with-diff`
18
20
  - Global install:
19
21
  - `npm i -g myte`
20
22
  - then run `myte bootstrap`
21
23
  - then run `myte sync-qaqc`
24
+ - then run `myte feedback-sync`
22
25
  - then run `myte query "What changed in logging?" --with-diff`
23
26
  - then run `myte update-team "Backend deploy completed; QAQC rerun queued."`
27
+ - then run `myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
24
28
  - then run `myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
25
29
  - No install:
26
30
  - `npx myte@latest bootstrap`
27
31
  - `npx myte@latest sync-qaqc`
32
+ - `npx myte@latest feedback-sync`
28
33
  - `npx myte@latest query "What changed in logging?" --with-diff`
29
34
  - `npx myte@latest update-team "Backend deploy completed; QAQC rerun queued."`
35
+ - `npx myte@latest update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
30
36
  - `npx myte@latest update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
31
37
 
32
38
  `npm install myte` by itself does not put `myte` on your shell PATH. Use `npx myte` or `npm exec myte -- ...` unless you installed globally.
@@ -118,6 +124,32 @@ Useful forms:
118
124
  - `npx myte sync-qaqc --dry-run --json`
119
125
  - `npx myte sync-qaqc --output-dir ./MyteCommandCenter`
120
126
 
127
+ ## Sync open feedback and PRD context
128
+
129
+ Run this from the wrapper root that contains the project's repo folders:
130
+
131
+ - `npx myte feedback-sync`
132
+ - or `npm exec myte -- feedback-sync`
133
+ - or `myte feedback-sync`
134
+
135
+ What it does:
136
+ - fetches a project-scoped feedback snapshot from the API using your project key
137
+ - defaults to open `Pending` feedback
138
+ - writes feedback cards under `MyteCommandCenter/data/feedback/items`
139
+ - writes readable PRD markdown copies under `MyteCommandCenter/data/feedback/prds` when available
140
+ - fully replaces the feedback-owned sync folders so stale feedback does not accumulate locally
141
+
142
+ Files written:
143
+ - `MyteCommandCenter/data/project.yml`
144
+ - `MyteCommandCenter/data/feedback/manifest.json`
145
+ - `MyteCommandCenter/data/feedback/items/<feedback_id>.yml`
146
+ - `MyteCommandCenter/data/feedback/prds/<feedback_id>.md` when PRD text exists
147
+
148
+ Useful forms:
149
+ - `npx myte feedback-sync --json`
150
+ - `npx myte feedback-sync --dry-run --json`
151
+ - `npx myte feedback-sync --status Pending --source User`
152
+
121
153
  ## Query with deterministic diff context
122
154
 
123
155
  Example:
@@ -214,6 +246,27 @@ Useful forms:
214
246
  - `npx myte update-team "Backend deploy completed." --print-context`
215
247
  - `npx myte update-team "Backend deploy completed." --json`
216
248
 
249
+ ## Owner updates
250
+
251
+ Use `update-owner` to send a direct project-owner email through the project-key Project Assistant surface.
252
+
253
+ Examples:
254
+
255
+ - `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
256
+ - `npx myte update-owner --subject "Board cleanup needed" --body-markdown "## Status\n- Phase 2 review pending"`
257
+ - `Get-Content -Raw .\updates\owner.md | npx myte update-owner --stdin --subject "Owner update"`
258
+
259
+ What it sends:
260
+
261
+ - `POST /api/project-assistant/update-owner`
262
+ - payload: `{ "subject": "...", "body_markdown": "..." }`
263
+
264
+ Notes:
265
+
266
+ - the owner recipient is resolved from the authenticated project
267
+ - the CLI cannot set an arbitrary recipient address
268
+ - the backend sends the email through Myte SMTP and stores a durable send record
269
+
217
270
  ## Client update drafts
218
271
 
219
272
  Use `update-client` to draft a branded client update email for owner review.
@@ -242,8 +295,10 @@ Notes:
242
295
  - `npm install myte`
243
296
  - `npx myte bootstrap`
244
297
  - `npx myte sync-qaqc`
298
+ - `npx myte feedback-sync`
245
299
  - `npx myte config --json`
246
300
  - `npx myte query "Summarize the current branch changes" --with-diff`
247
301
  - `npx myte create-prd ./drafts/auth-prd.md`
248
302
  - `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
303
+ - `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
249
304
  - `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "myte",
3
- "version": "0.0.7",
3
+ "version": "0.0.8",
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.7"
19
+ "@mytegroupinc/myte-core": "0.0.8"
20
20
  }
21
21
  }