myte 0.0.17 → 0.0.19

package/README.md

@@ -13,6 +13,7 @@ Use one of these flows:
   - then run `npx myte config --json`
   - then run `npx myte bootstrap`
   - then run `npx myte run-qaqc --mission-ids M001 --wait --sync`
+  - then run `npx myte mission status --mission-ids M001 --status done`
   - then run `npx myte sync-qaqc`
   - then run `npx myte feedback-sync`
   - then run `npx myte suggestions sync`
@@ -29,6 +30,7 @@ Use one of these flows:
   - then run `myte ai "Explain this repository"`
   - then run `myte bootstrap`
   - then run `myte run-qaqc --mission-ids M001 --wait --sync`
+  - then run `myte mission status --mission-ids M001 --status done`
   - then run `myte sync-qaqc`
   - then run `myte feedback-sync`
   - then run `myte suggestions sync`
@@ -43,6 +45,7 @@ Use one of these flows:
   - `npx myte@latest ai "Explain this repository"`
   - `npx myte@latest bootstrap`
   - `npx myte@latest run-qaqc --mission-ids M001 --wait --sync`
+  - `npx myte@latest mission status --mission-ids M001 --status done`
   - `npx myte@latest sync-qaqc`
   - `npx myte@latest feedback-sync`
   - `npx myte@latest suggestions sync`
@@ -153,6 +156,19 @@ Useful forms:
 - `npx myte run-qaqc --mission-ids "M001,M002" --wait`
 - `npx myte run-qaqc --mission-ids "M001,M002" --wait --sync --json`
 
+## Update mission status from the IDE
+
+- `npx myte mission status --mission-ids "M001,M002" --status done`
+- or `npm exec myte -- mission status --mission-ids "M001,M002" --status done`
+- or `myte mission status --mission-ids "M001,M002" --status done`
+
+What it does:
+- updates one or many mission business ids through the project-key API
+- updates the same mission `status` field used by the app board and mission routes
+- accepts `todo`, `in_progress`, and `done` aliases and normalizes them before sending
+- sends the canonical backend mission statuses: `Todo`, `In Progress`, or `Done`
+- only changes mission state; it does not queue QAQC and it does not sync `MyteCommandCenter/data/qaqc.yml`
+
 ## Sync active mission QAQC context
 
 Run this from the wrapper root that contains the project's repo folders:
@@ -179,7 +195,7 @@ Useful forms:
 - `npx myte sync-qaqc --dry-run --json`
 - `npx myte sync-qaqc --output-dir ./MyteCommandCenter`
 
-## Sync open feedback and PRD context
+## Sync feedback and PRD context
 
 Run this from the wrapper root that contains the project's repo folders:
 
@@ -189,7 +205,7 @@ Run this from the wrapper root that contains the project's repo folders:
 
 What it does:
 - fetches a project-scoped feedback snapshot from the API using your project key
-- defaults to open `Pending` feedback
+- defaults to pending feedback; use `--status` when you want a different slice
 - writes one deterministic feedback snapshot under `MyteCommandCenter/data/feedback.yml`
 - keeps feedback metadata plus conversation turns in `feedback.yml`
 - writes full PRD markdown/text into `MyteCommandCenter/PRD/feedback-sync/*.md` and stores a pointer in `feedback.yml`
@@ -395,6 +411,7 @@ Notes:
 
 - `npm install myte`
 - `npx myte bootstrap`
+- `npx myte mission status --mission-ids "M001,M002" --status done`
 - `npx myte sync-qaqc`
 - `npx myte feedback-sync`
 - `npx myte suggestions sync`

package/package.json

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