myte 0.0.37 → 0.0.40

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 CHANGED
@@ -160,10 +160,10 @@ Feedback comments nuance:
160
160
  - `ai`: use the Myte AI gateway
161
161
  - `mytecody`: MyteCody team launcher installed by this package. It supports
162
162
  `doctor`, `doctor --probe-gateway`, `update --dry-run`, and `update`.
163
- On first coding run, it installs the branded MyteCody engine from the Myte
164
- release manifest into a user-local Myte cache after signature/hash checks.
165
- Coding execution requires that engine, a reachable Myte AI Cody gateway, and
166
- `MYTEAI_API_KEY`.
163
+ On first coding run, it installs the branded MyteCody engine and signed
164
+ client assets from the Myte release manifest into a user-local Myte cache
165
+ after signature/hash checks. Coding execution requires those assets, a
166
+ reachable Myte AI Cody gateway, and `MYTEAI_API_KEY`.
167
167
  - `mytecody doctor` reports both the signed MyteCody engine state and this npm
168
168
  package version. `mytecody update` updates the engine only. Use
169
169
  `npm install -g myte@latest` to update the launcher and the Myte API CLI
@@ -174,8 +174,9 @@ Feedback comments nuance:
174
174
  ## Notes
175
175
 
176
176
  - The package ships the CLI only. Internal rollout notes, validation logs, and project-specific operating docs are not part of the public npm contract.
177
- - The package does not bundle the large MyteCody engine binary. The `mytecody`
178
- launcher installs or updates it through the Myte release manifest.
177
+ - The package does not bundle the large MyteCody engine binary or the async
178
+ Responses bridge implementation. The `mytecody` launcher installs or updates
179
+ signed engine/client assets through the Myte release manifest.
179
180
  - `mytecody update` is intentionally engine-scoped. npm package updates use
180
181
  `npm install -g myte@latest`.
181
182
  - The public `myte` package is the supported entrypoint. The scoped `@mytegroupinc/myte-core` package is the implementation dependency used by the wrapper.
@@ -1,7 +1,8 @@
1
1
  # Third-Party Notices
2
2
 
3
3
  The `myte` package exposes the `mytecody` command. The command installs and
4
- launches a branded MyteCody engine from a Myte release manifest.
4
+ launches a branded MyteCody engine and signed client assets from a Myte release
5
+ manifest.
5
6
 
6
7
  The branded MyteCody engine is derived from the OpenAI Codex open-source
7
8
  project, version baseline `0.139.0`, licensed under Apache-2.0.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "myte",
3
- "version": "0.0.37",
3
+ "version": "0.0.40",
4
4
  "description": "Myte developer CLI.",
5
5
  "type": "commonjs",
6
6
  "license": "MIT",
@@ -19,6 +19,6 @@
19
19
  "node": ">=18"
20
20
  },
21
21
  "dependencies": {
22
- "@mytegroupinc/myte-core": "0.0.37"
23
- }
24
- }
22
+ "@mytegroupinc/myte-core": "0.0.40"
23
+ }
24
+ }