myte 0.0.14 → 0.0.16

package/README.md

@@ -8,6 +8,8 @@ Use one of these flows:
 
 - Local dependency in your project:
   - `npm install myte`
+  - then run `npx myte ai "Explain this repository"`
+  - then run `npx myte ai "Return a JSON object with risks and next_steps" --json-response`
   - then run `npx myte config --json`
   - then run `npx myte bootstrap`
   - then run `npx myte run-qaqc --mission-ids M001 --wait --sync`
@@ -24,6 +26,7 @@ Use one of these flows:
   - or `npm exec myte -- query "What changed in logging?" --with-diff`
 - Global install:
   - `npm i -g myte`
+  - then run `myte ai "Explain this repository"`
   - then run `myte bootstrap`
   - then run `myte run-qaqc --mission-ids M001 --wait --sync`
   - then run `myte sync-qaqc`
@@ -37,6 +40,7 @@ Use one of these flows:
   - 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 ai "Explain this repository"`
   - `npx myte@latest bootstrap`
   - `npx myte@latest run-qaqc --mission-ids M001 --wait --sync`
   - `npx myte@latest sync-qaqc`
@@ -56,12 +60,14 @@ Important:
 - `npm install myte` gives the user everything needed locally.
 - The normal local command is `npx myte ...` or `npm exec myte -- ...`.
 - Bare `myte ...` only works after `npm i -g myte`.
+- `myte ai` uses `MYTEAI_API_KEY` and the `api.myte.ai` gateway.
 
 ## Requirements
 
 - Node `18+`
 - macOS, Linux, and Windows are supported
 - `git` available in `PATH` for `--with-diff`
+- `MYTEAI_API_KEY=<inference_api_key>` available in your shell or in a `.env` for `myte ai`
 - `MYTE_API_KEY=<project_api_key>` available in your shell or in a `.env`
 - the CLI searches for `.env` in the current folder and then up parent directories
 - For deterministic diff capture, run from:
@@ -78,6 +84,17 @@ Run this first when onboarding on a new machine:
 - or `npm exec myte -- config --json`
 - or `npx myte@latest config --json`
 
+## Myte AI gateway
+
+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`.
+
+Examples:
+
+- `npx myte ai "Explain what this repository does"`
+- `npx myte ai "Return a JSON object with risks and next_steps" --json-response`
+- `npm exec myte -- ai "Summarize this file"`
+- `myte ai "Return clean JSON only" --json-response`
+
 It confirms:
 - the API key resolves to the expected project
 - which repo names the project is configured with
@@ -172,13 +189,15 @@ What it does:
 - fetches a project-scoped feedback snapshot from the API using your project key
 - defaults to open `Pending` feedback
 - writes one deterministic feedback snapshot under `MyteCommandCenter/data/feedback.yml`
-- includes readable PRD markdown inline when available
+- 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`
 - fully replaces the aggregated feedback sync file so stale feedback does not accumulate locally
 - does not delete `MyteCommandCenter/data/missions/*.yml`
 
 Files written:
 - `MyteCommandCenter/data/project.yml`
 - `MyteCommandCenter/data/feedback.yml`
+- `MyteCommandCenter/PRD/feedback-sync/*.md`
 
 Useful forms:
 - `npx myte feedback-sync --json`

package/package.json

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