myte 0.0.16 → 0.0.18
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.
- package/README.md +21 -2
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -13,6 +13,7 @@ Use one of these flows:
|
|
|
13
13
|
- then run `npx myte config --json`
|
|
14
14
|
- then run `npx myte bootstrap`
|
|
15
15
|
- then run `npx myte run-qaqc --mission-ids M001 --wait --sync`
|
|
16
|
+
- then run `npx myte mission status --mission-ids M001 --status done`
|
|
16
17
|
- then run `npx myte sync-qaqc`
|
|
17
18
|
- then run `npx myte feedback-sync`
|
|
18
19
|
- then run `npx myte suggestions sync`
|
|
@@ -29,6 +30,7 @@ Use one of these flows:
|
|
|
29
30
|
- then run `myte ai "Explain this repository"`
|
|
30
31
|
- then run `myte bootstrap`
|
|
31
32
|
- then run `myte run-qaqc --mission-ids M001 --wait --sync`
|
|
33
|
+
- then run `myte mission status --mission-ids M001 --status done`
|
|
32
34
|
- then run `myte sync-qaqc`
|
|
33
35
|
- then run `myte feedback-sync`
|
|
34
36
|
- then run `myte suggestions sync`
|
|
@@ -43,6 +45,7 @@ Use one of these flows:
|
|
|
43
45
|
- `npx myte@latest ai "Explain this repository"`
|
|
44
46
|
- `npx myte@latest bootstrap`
|
|
45
47
|
- `npx myte@latest run-qaqc --mission-ids M001 --wait --sync`
|
|
48
|
+
- `npx myte@latest mission status --mission-ids M001 --status done`
|
|
46
49
|
- `npx myte@latest sync-qaqc`
|
|
47
50
|
- `npx myte@latest feedback-sync`
|
|
48
51
|
- `npx myte@latest suggestions sync`
|
|
@@ -88,6 +91,8 @@ Run this first when onboarding on a new machine:
|
|
|
88
91
|
|
|
89
92
|
Use `myte ai` as the thin inference gateway client. The npm package does not ship models or backend internals; it sends your request to `api.myte.ai` with `MYTEAI_API_KEY`.
|
|
90
93
|
|
|
94
|
+
`--json-response` asks for strict JSON and now sends both `myte_json_response: true` and the OpenAI-compatible `response_format: { type: "json_object" }` shape. On the public developer API, that strict-JSON path also defaults to `medium` reasoning unless the caller explicitly overrides reasoning.
|
|
95
|
+
|
|
91
96
|
Examples:
|
|
92
97
|
|
|
93
98
|
- `npx myte ai "Explain what this repository does"`
|
|
@@ -151,6 +156,19 @@ Useful forms:
|
|
|
151
156
|
- `npx myte run-qaqc --mission-ids "M001,M002" --wait`
|
|
152
157
|
- `npx myte run-qaqc --mission-ids "M001,M002" --wait --sync --json`
|
|
153
158
|
|
|
159
|
+
## Update mission status from the IDE
|
|
160
|
+
|
|
161
|
+
- `npx myte mission status --mission-ids "M001,M002" --status done`
|
|
162
|
+
- or `npm exec myte -- mission status --mission-ids "M001,M002" --status done`
|
|
163
|
+
- or `myte mission status --mission-ids "M001,M002" --status done`
|
|
164
|
+
|
|
165
|
+
What it does:
|
|
166
|
+
- updates one or many mission business ids through the project-key API
|
|
167
|
+
- updates the same mission `status` field used by the app board and mission routes
|
|
168
|
+
- accepts `todo`, `in_progress`, and `done` aliases and normalizes them before sending
|
|
169
|
+
- sends the canonical backend mission statuses: `Todo`, `In Progress`, or `Done`
|
|
170
|
+
- only changes mission state; it does not queue QAQC and it does not sync `MyteCommandCenter/data/qaqc.yml`
|
|
171
|
+
|
|
154
172
|
## Sync active mission QAQC context
|
|
155
173
|
|
|
156
174
|
Run this from the wrapper root that contains the project's repo folders:
|
|
@@ -177,7 +195,7 @@ Useful forms:
|
|
|
177
195
|
- `npx myte sync-qaqc --dry-run --json`
|
|
178
196
|
- `npx myte sync-qaqc --output-dir ./MyteCommandCenter`
|
|
179
197
|
|
|
180
|
-
## Sync
|
|
198
|
+
## Sync feedback and PRD context
|
|
181
199
|
|
|
182
200
|
Run this from the wrapper root that contains the project's repo folders:
|
|
183
201
|
|
|
@@ -187,7 +205,7 @@ Run this from the wrapper root that contains the project's repo folders:
|
|
|
187
205
|
|
|
188
206
|
What it does:
|
|
189
207
|
- fetches a project-scoped feedback snapshot from the API using your project key
|
|
190
|
-
- defaults to
|
|
208
|
+
- defaults to all non-archived feedback; use `--status` when you want a narrower slice
|
|
191
209
|
- writes one deterministic feedback snapshot under `MyteCommandCenter/data/feedback.yml`
|
|
192
210
|
- keeps feedback metadata plus conversation turns in `feedback.yml`
|
|
193
211
|
- writes full PRD markdown/text into `MyteCommandCenter/PRD/feedback-sync/*.md` and stores a pointer in `feedback.yml`
|
|
@@ -393,6 +411,7 @@ Notes:
|
|
|
393
411
|
|
|
394
412
|
- `npm install myte`
|
|
395
413
|
- `npx myte bootstrap`
|
|
414
|
+
- `npx myte mission status --mission-ids "M001,M002" --status done`
|
|
396
415
|
- `npx myte sync-qaqc`
|
|
397
416
|
- `npx myte feedback-sync`
|
|
398
417
|
- `npx myte suggestions sync`
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "myte",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.18",
|
|
4
4
|
"description": "Myte developer CLI (Project Assistant + Myte AI gateway).",
|
|
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.
|
|
19
|
+
"@mytegroupinc/myte-core": "0.0.18"
|
|
20
20
|
}
|
|
21
21
|
}
|