myte 0.0.32 → 0.0.34

package/README.md

@@ -25,10 +25,11 @@ No install:
 
 - Node `18+`
 - macOS, Linux, or Windows
-- `MYTE_API_KEY=<project_api_key>` in your shell or workspace `.env`
-- `MYTEAI_API_KEY=<inference_api_key>` only for `myte ai`
-- `git` in `PATH` only for `query --with-diff`
-- No runtime npm dependencies beyond the Myte packages themselves.
+- `MYTE_API_KEY=<project_api_key>` in your shell or workspace `.env`
+- `MYTEAI_API_KEY=<inference_api_key>` only for `myte ai`
+- `MYTEAI_API_KEY=<inference_api_key>` for `mytecody`
+- `git` in `PATH` only for `query --with-diff`
+- No runtime npm dependencies beyond the Myte packages themselves.
 
 The CLI searches for `.env` in the current folder and then up parent directories.
 
@@ -48,11 +49,12 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `npx myte feedback submit --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
 - `npx myte feedback reviews --status open`
 - `npx myte feedback revise --request-id <id> --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
-- `npx myte feedback review --request-id <id> --action approve --reason "Looks correct"`
-- `npx myte feedback review --request-ids "<id1,id2>" --action approve --reason "Batch approval"`
-- `npx myte feedback move --feedback-id <id> --to-state in_progress --reason "Started"`
-- `npx myte feedback move --feedback-ids "<id1,id2>" --to-state in_progress --reason "Batch move"`
-- `npx myte feedback undo --feedback-id <id> --event-id <event_id> --reason "Undo accidental move"`
+- `npx myte feedback review --request-id <id> --action approve --reason "Looks correct"`
+- `npx myte feedback review --request-ids "<id1,id2>" --action approve --reason "Batch approval"`
+- `npx myte feedback move --feedback-id <id> --to-state in_progress --reason "Started"`
+- `npx myte feedback move --feedback-ids "<id1,id2>" --to-state in_progress --reason "Batch move"`
+- `npx myte feedback comment --feedback-id <id> --body-file ./updates/feedback-comment.md`
+- `npx myte feedback undo --feedback-id <id> --event-id <event_id> --reason "Undo accidental move"`
 - `npx myte feedback prd-versions --feedback-id <id>`
 - `npx myte feedback prd-diff --feedback-id <id> --version-id <version_id> --compare-to <base_version_id>`
 - `npx myte feedback apply --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
@@ -61,8 +63,12 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `npx myte query "Summarize the current branch changes" --with-diff`
 - `npx myte create-prd ./drafts/auth-prd.md`
 - `npx myte update-team "Backend deploy completed."`
-- `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
-- `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
+- `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
+- `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
+- `npx mytecody doctor`
+- `npx mytecody doctor --probe-gateway`
+- `npx mytecody update --dry-run`
+- `npx mytecody update`
 
 ## Behavior
 
@@ -72,7 +78,8 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `mission status` and `mission archive` refresh local bootstrap + mission-ops state by default after a successful mutation. Use `--no-sync` only when you intentionally want to skip the local refresh.
 - `feedback status|edit|assign|archive` writes local review artifacts under `MyteCommandCenter/reviews/feedback`; `feedback submit|revise|reviews|review` routes proposed edits through the backend owner-review membrane.
 - `feedback review --request-ids` sends one backend batch review request with grouped notifications; do not loop single-review calls for batch decisions.
-- `feedback move|undo|prd-versions|prd-diff|history` calls the project-key Feedback API while authorization, stale snapshot checks, allowed transitions, and history remain enforced by the backend. `feedback move --feedback-ids` sends one batch board move request.
+- `feedback move|comment|undo|prd-versions|prd-diff|history` calls the project-key Feedback API while authorization, stale snapshot checks, allowed transitions, and history remain enforced by the backend. `feedback move --feedback-ids` sends one batch board move request.
+- `feedback comment` creates text-only feedback-specific comments. Attachments remain web UI only for this project-key endpoint.
 - `feedback-sync` excludes archived Feedback from normal `MyteCommandCenter` state. Project-key API/CLI can archive authorized Feedback, but Feedback unarchive/restore is web UI only.
 - `feedback validate|apply` remains available for validation and owner-direct apply paths.
 - `query --with-diff` is stricter than the snapshot commands. It requires project repositories to be configured by the project owner or builder, and it requires at least one matching local project repo to be resolved for diff collection.
@@ -99,7 +106,7 @@ Recommended agent flow:
 6. Use `myte feedback move` only for direct board movement that is intentionally audited, with a clear `--reason`; use `--feedback-ids` for batch moves or batch archive.
 7. Use `myte suggestions create|revise|review` for mission review threads. Valid create `change_type` values are exactly `update` and `create`; revisions keep the existing thread type and must not include `change_type`.
 8. Use `myte mission archive` for project-key mission lifecycle archival. Archive requires Project Owner or elevated delegate capability; restore is web-only from the archived missions board.
-9. Use `myte update-team "<content>"` for project/team comments through `/api/project-assistant/project-comment`.
+9. Use `myte update-team "<content>"` for project/team comments through `/api/project-assistant/project-comment`, and `myte feedback comment --feedback-id <id> --body-file ./comment.md` for feedback-specific implementation notes.
 
 PRD document contract:
 
@@ -131,11 +138,12 @@ Preferred file shape:
 Full PRD content goes here.
 ````
 
-Feedback comments nuance:
-
-- `myte feedback-sync` reads existing feedback comment turns and stores them in `MyteCommandCenter/data/feedback.yml`.
-- The web product supports feedback-specific comment create/fetch through JWT-authenticated `/api/feedbacks/<feedback_id>/comments`.
-- The project-key npm CLI does not currently expose `myte feedback comment <feedback_id> "<text>"`. Add a Project Assistant route and CLI command before documenting that as supported.
+Feedback comments nuance:
+
+- `myte feedback-sync` reads existing feedback comment turns and stores them in `MyteCommandCenter/data/feedback.yml`.
+- The web product supports feedback-specific comment create/fetch through JWT-authenticated `/api/feedbacks/<feedback_id>/comments`.
+- The project-key npm CLI supports `myte feedback comment --feedback-id <id> --body "..."` and `--body-file ./comment.md`.
+- Project-key feedback comments are text-only in this slice and cap content at 500,000 characters. Use the web UI when attachments are required.
 
 ## Commands
 
@@ -146,17 +154,27 @@ Feedback comments nuance:
 - `mission archive`: archive missions without hard delete
 - `sync-qaqc`: refresh active mission QAQC context locally
 - `feedback-sync`: refresh feedback and PRD context locally
-- `feedback status|edit|assign|archive|submit|revise|reviews|review|move|undo|prd-versions|prd-diff|validate|apply|history|get`: create reviewable feedback artifacts and operate the governed Feedback API
+- `feedback status|edit|assign|archive|submit|revise|reviews|review|move|comment|undo|prd-versions|prd-diff|validate|apply|history|get`: create reviewable feedback artifacts and operate the governed Feedback API
 - `suggestions sync|create|revise|review`: work with mission suggestion workflow state
 - `query`: ask the project assistant, optionally with local diff context
-- `ai`: use the Myte AI gateway
-- `create-prd`: upload deterministic PRD markdown as the stored renderable PRD document; use `description` only as the short card summary
+- `ai`: use the Myte AI gateway
+- `mytecody`: MyteCody team launcher installed by this package. It supports
+  `doctor`, `doctor --probe-gateway`, `update --dry-run`, and `update`.
+  On first coding run, it installs the branded MyteCody engine from the Myte
+  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`.
+- `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
 
 ## Notes
 
-- 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 public `myte` package is the supported entrypoint. The scoped `@mytegroupinc/myte-core` package is the implementation dependency used by the wrapper.
+- 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.
+- 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.
 
 ## Mission Action Map
 
@@ -192,9 +210,10 @@ After `bootstrap`, find ids locally:
 | `feedback submit` | Sends a local proposal artifact to the backend as a review request. | Does not mutate live feedback before approval. |
 | `feedback revise` | Resubmits the original submitter's request after `request_changes`. | Only valid for the original submitter and `needs_changes` requests. |
 | `feedback reviews` | Lists review requests or fetches one request by `--request-id`. | Read-only; response includes backend permissions. |
-| `feedback review` | Approves, rejects, requests changes, or cancels one review request, or a batch with `--request-ids`. | Backend restricts approval/review decisions to Project Owner or elevated delegate for Feedback scope; batch review uses one grouped notification path. |
-| `feedback move` | Moves a card or batch of cards across allowed board states directly with an audit event. | `--feedback-ids` sends one batch request. Blocked with `pending_feedback_review` while an active linked review request exists; governed states such as archive/reject/deploy/freeze remain backend-authorized. Project-key unarchive is not supported. |
-| `feedback undo` | Reverses an audited board event when there is no conflict. | Backend validates event ownership/project scope and conflict state. |
+| `feedback review` | Approves, rejects, requests changes, or cancels one review request, or a batch with `--request-ids`. | Backend restricts approval/review decisions to Project Owner or elevated delegate for Feedback scope; batch review uses one grouped notification path. |
+| `feedback move` | Moves a card or batch of cards across allowed board states directly with an audit event. | `--feedback-ids` sends one batch request. Blocked with `pending_feedback_review` while an active linked review request exists; governed states such as archive/reject/deploy/freeze remain backend-authorized. Project-key unarchive is not supported. |
+| `feedback comment` | Creates a text-only comment on one Feedback item. | Backend checks project-key access, owner/assigned permission, idempotency, and the 500,000-character content cap. Attachments remain web UI only. |
+| `feedback undo` | Reverses an audited board event when there is no conflict. | Backend validates event ownership/project scope and conflict state. |
 | `feedback prd-versions` | Lists retained PRD baselines/revisions for a feedback item. | Read-only; old S3 objects are retained by reference. |
 | `feedback prd-diff` | Fetches backend-generated text diff for PRD versions. | Read-only; backend controls version access. |
 | `feedback history` | Lists audited feedback board/refinement events. | Read-only; backend checks project access. |
@@ -250,9 +269,10 @@ Mutation routes:
 - `POST /api/project-assistant/feedback-review-requests/batch-review`
 - `POST /api/project-assistant/feedback-review-requests/<request_id>/request-changes`
 - `POST /api/project-assistant/feedback-review-requests/<request_id>/cancel`
-- `POST /api/project-assistant/feedback/<feedback_id>/board-move`
-- `POST /api/project-assistant/feedback/batch-board-move`
-- `POST /api/project-assistant/feedback/<feedback_id>/events/<event_id>/undo`
+- `POST /api/project-assistant/feedback/<feedback_id>/board-move`
+- `POST /api/project-assistant/feedback/batch-board-move`
+- `POST /api/project-assistant/feedback/<feedback_id>/comments`
+- `POST /api/project-assistant/feedback/<feedback_id>/events/<event_id>/undo`
 - `POST /api/project-assistant/suggestions`
 - `POST /api/project-assistant/suggestions/revise`
 - `POST /api/project-assistant/suggestions/review`

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,10 @@
+# Third-Party Notices
+
+The `myte` package exposes the `mytecody` command. The command installs and
+launches a branded MyteCody engine from a Myte release manifest.
+
+The branded MyteCody engine is derived from the OpenAI Codex open-source
+project, version baseline `0.139.0`, licensed under Apache-2.0.
+
+Myte names, marks, logos, terminal branding, and product design are separate
+Myte-owned brand assets.

package/TRADEMARKS.md

@@ -0,0 +1,10 @@
+# Trademarks
+
+Myte, Myte AI, MyteCody, "MYTE CODY - Your Tech Your Way", logo assets, terminal
+animation assets, and related product branding are Myte-owned marks and brand
+assets.
+
+OpenAI and Codex are trademarks or project names of their respective owners.
+MyteCody uses a Codex-derived open-source engine under the applicable open
+source license, but MyteCody is a Myte product surface and is not presented as
+an official OpenAI product.

package/bin/mytecody.js

@@ -0,0 +1,19 @@
+#!/usr/bin/env node
+"use strict";
+
+const cody = require("@mytegroupinc/myte-core/mytecody-cli");
+
+if (!cody || typeof cody.run !== "function") {
+  console.error("mytecody core entrypoint is unavailable.");
+  process.exit(1);
+}
+
+Promise.resolve(cody.run(process.argv.slice(2))).then(
+  (code) => {
+    process.exitCode = Number.isInteger(code) ? code : 0;
+  },
+  (err) => {
+    console.error("Unexpected error:", err?.message || err);
+    process.exitCode = 1;
+  },
+);

package/package.json

@@ -1,21 +1,24 @@
 {
   "name": "myte",
-  "version": "0.0.32",
+  "version": "0.0.34",
   "description": "Myte developer CLI.",
   "type": "commonjs",
   "license": "MIT",
-  "files": [
-    "README.md",
-    "bin",
-    "package.json"
+  "files": [
+    "README.md",
+    "THIRD_PARTY_NOTICES.md",
+    "TRADEMARKS.md",
+    "bin",
+    "package.json"
   ],
-  "bin": {
-    "myte": "bin/myte.js"
-  },
+  "bin": {
+    "myte": "bin/myte.js",
+    "mytecody": "bin/mytecody.js"
+  },
   "engines": {
     "node": ">=18"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.32"
+    "@mytegroupinc/myte-core": "0.0.34"
   }
 }