myte 0.0.36 → 0.0.37

package/README.md

@@ -164,6 +164,10 @@ Feedback comments nuance:
   release manifest into a user-local Myte cache after signature/hash checks.
   Coding execution requires that engine, a reachable Myte AI Cody gateway, and
   `MYTEAI_API_KEY`.
+- `mytecody doctor` reports both the signed MyteCody engine state and this npm
+  package version. `mytecody update` updates the engine only. Use
+  `npm install -g myte@latest` to update the launcher and the Myte API CLI
+  commands shipped by npm.
 - `create-prd`: upload deterministic PRD markdown as the stored renderable PRD document; use `description` only as the short card summary
 - `update-team`, `update-owner`, `update-client`: send project updates through the project-key surface
 
@@ -172,6 +176,8 @@ Feedback comments nuance:
 - The package ships the CLI only. Internal rollout notes, validation logs, and project-specific operating docs are not part of the public npm contract.
 - The package does not bundle the large MyteCody engine binary. The `mytecody`
   launcher installs or updates it through the Myte release manifest.
+- `mytecody update` is intentionally engine-scoped. npm package updates use
+  `npm install -g myte@latest`.
 - The public `myte` package is the supported entrypoint. The scoped `@mytegroupinc/myte-core` package is the implementation dependency used by the wrapper.
 - See `THIRD_PARTY_NOTICES.md` and `TRADEMARKS.md` for Codex lineage and Myte
   brand notices.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "myte",
-  "version": "0.0.36",
+  "version": "0.0.37",
   "description": "Myte developer CLI.",
   "type": "commonjs",
   "license": "MIT",
@@ -19,6 +19,6 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.36"
+    "@mytegroupinc/myte-core": "0.0.37"
   }
 }