myte 0.0.4 → 0.0.6

package/README.md

@@ -9,12 +9,18 @@ Use one of these flows:
 - Local dependency in your project:
   - `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`
   - 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`
 - No install:
+  - `npx myte@latest bootstrap`
+  - `npx myte@latest sync-qaqc`
   - `npx myte@latest query "What changed in logging?" --with-diff`
 
 `npm install myte` by itself does not put `myte` on your shell PATH. Use `npx myte` or `npm exec myte -- ...` unless you installed globally.
@@ -50,6 +56,62 @@ It confirms:
 - which repo names the project is configured with
 - which of those repos were found locally
 
+## Bootstrap Command Center cards
+
+Run this from the wrapper root that contains the project's repo folders:
+
+- `npx myte bootstrap`
+- or `npm exec myte -- bootstrap`
+- or `myte bootstrap`
+
+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`
+- `MyteCommandCenter/data/phases/*.yml`
+- `MyteCommandCenter/data/epics/*.yml`
+- `MyteCommandCenter/data/stories/*.yml`
+- `MyteCommandCenter/data/missions/*.yml`
+- `MyteCommandCenter/data/bootstrap-manifest.json`
+
+Useful forms:
+- `npx myte bootstrap --json`
+- `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:
@@ -97,10 +159,10 @@ Preferred file format matches `script/MyteCodyPRD.py`:
 ```myte-kanban
 {
   "title": "Authentication PRD",
+  "description": "Short card summary shown in the feedback list",
   "priority": "Medium",
   "assigned_user_email": "dev@mytegroup.com",
-  "tags": ["mission-board"],
-  "feedback_text": "Short card summary"
+  "tags": ["mission-board"]
 }
 ```
 
@@ -112,10 +174,25 @@ Detailed markdown body here.
 Raw markdown also works:
 - include a top-level `# Title`
 - or pass `--title "..."` when using `--stdin`
+- pass `--description "..."` if you want an explicit feedback description/card summary
+
+Deterministic field mapping:
+- Required: a valid project API key, the PRD markdown body, and a title.
+- `title` maps to the feedback title.
+- `description` maps to the feedback description/card summary. Legacy `feedback_text` is still accepted for older payloads.
+- The markdown body after the metadata block, or the full raw markdown file when no metadata block is used, is stored verbatim as PRD content.
+- The backend uses that stored PRD markdown/text to generate the downloadable PRD DOCX.
+- Additional structured fields should go in the `myte-kanban` JSON block. Supported keys include `priority`, `status`, `tags`, `assigned_user_email`, `assigned_user_id`, `due_date`, `repo_name`, `repo_id`, `preview_url`, and `source`.
+
+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`
 
 ## 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`

package/package.json

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