myte 0.0.24 → 0.0.26

package/README.md

@@ -28,6 +28,7 @@ No install:
 - `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.
 
 The CLI searches for `.env` in the current folder and then up parent directories.
 
@@ -54,6 +55,8 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `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`
 - `npx myte suggestions sync`
+- `npx myte mission archive --mission-ids "M001" --reason "Duplicate disposable mission"`
+- `npx myte mission restore --mission-ids "M001" --status todo --reason "Restore after review"`
 - `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."`
@@ -63,6 +66,8 @@ The CLI searches for `.env` in the current folder and then up parent directories
 ## Behavior
 
 - `bootstrap`, `sync-qaqc`, `feedback-sync`, and `suggestions sync` write project-scoped local context under `MyteCommandCenter` in the current workspace unless `--output-dir` is provided.
+- `bootstrap` writes mission cards and mission suggestion thread state together; agents should run it before looking for mission or suggestion ids.
+- `mission status` is active-state only (`todo`, `in_progress`, `done`). Use `mission archive` and `mission restore` for lifecycle archival.
 - `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 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 validate|apply` remains available for validation and owner-direct apply paths.
@@ -70,19 +75,76 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - If diff-scoped repo configuration is missing or no local project repo can be resolved, `query --with-diff` exits with an error instead of silently dropping diff context.
 - Most markdown files are excluded from diff context by default so code and runtime configuration changes dominate the payload. Key instruction files such as `README.md` and `AGENTS.md` remain eligible.
 
+## Agent Usage Contract
+
+Codex, Claude, and other coding agents should use one project-scoped key per workspace:
+
+```bash
+MYTE_API_KEY=<project_api_key>
+```
+
+The key resolves the project server-side. Agents should not pass `project_id` manually for normal CLI commands, and they should not call account-scoped web/JWT endpoints with this key.
+
+Recommended agent flow:
+
+1. Run `myte config --json` to confirm the project, API base, configured repos, and local workspace detection.
+2. Run `myte bootstrap --json`, `myte feedback-sync --json`, or `myte sync-qaqc --json` to hydrate local context under `MyteCommandCenter`. Use `myte suggestions sync --json` only for narrow mission-review refreshes after bootstrap.
+3. Use `myte query "<goal/evidence/ask>" --with-diff` when local code changes matter.
+4. Use `myte create-prd <file.md>` only after the PRD markdown has been reviewed by a human. The file body is the PRD document; `--description` is only the short board/card summary.
+5. Use `myte feedback status|edit|assign|archive` to create reviewable local artifacts, then `feedback submit` and `feedback review` for the owner-review membrane.
+6. Use `myte feedback move` only for direct board movement that is intentionally audited, with a clear `--reason`.
+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` and `myte mission restore` for mission lifecycle archive/restore. Archive/restore require Project Owner or elevated delegate capability.
+9. Use `myte update-team "<content>"` for project/team comments through `/api/project-assistant/project-comment`.
+
+PRD document contract:
+
+- Always put the complete PRD in the markdown file passed to `myte create-prd`.
+- `title` maps to the feedback/board title.
+- `description` maps to the short feedback/card summary and must not contain the full PRD.
+- The markdown body is sent as `prd_markdown` or `ticket_markdown`, stored as the PRD document source, mirrored as PRD text for search/sync, and used by the backend to generate the PRD DOCX.
+- The UI renders the PRD from the stored document text, not from the card description.
+
+Preferred file shape:
+
+````markdown
+```myte-kanban
+{
+  "title": "Feedback Search PRD",
+  "description": "Improve feedback search across titles, descriptions, and stored PRD text.",
+  "priority": "Medium",
+  "tags": ["feedback", "search"]
+}
+```
+
+# Feedback Search PRD
+
+## Goal
+
+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.
+
 ## Commands
 
 - `config`: verify the project key and inspect local repo resolution
 - `bootstrap`: write project board context locally
 - `run-qaqc`: queue QAQC for explicit mission ids
-- `mission status`: update mission state
+- `mission status`: update active mission state
+- `mission archive`: archive missions without hard delete
+- `mission restore`: restore archived missions to an active state
 - `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
 - `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
+- `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
@@ -90,6 +152,28 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - 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.
 
+## Mission Action Map
+
+| Action | Command / Surface | Contract |
+| --- | --- | --- |
+| Sync mission cards and review threads | `myte bootstrap --json` | Refreshes `MyteCommandCenter/data/missions/*.yml`, project structure, and `MyteCommandCenter/data/mission-ops.yml`. |
+| Sync only mission review threads | `myte suggestions sync --json` | Narrow refresh for `mission-ops.yml` after bootstrap or a mutation. |
+| Suggest edit to existing mission | `myte suggestions create` with `change_type: update` and `mission_id` | Creates or appends to an active review thread; live mission is unchanged until approval. |
+| Suggest new mission | `myte suggestions create` with `change_type: create` | Requires `change_set.title` and `change_set.description`; mission card is created only after approval. |
+| Revise a suggestion | `myte suggestions revise` with `suggestion_id` | Adds another revision to the same thread. Do not include `change_type`. |
+| Review a suggestion | `myte suggestions review` with `review_action: approve|request_changes|reject` | Project Owner or elevated mission-review delegate required. |
+| Update mission status | `myte mission status --mission-ids "M001" --status todo|in_progress|done` | Active status update only. |
+| Archive mission | `myte mission archive --mission-ids "M001" --reason "..."` | Project Owner or elevated delegate required. Keeps the mission record and hides it from normal board/bootstrap state. |
+| Restore mission | `myte mission restore --mission-ids "M001" --status todo|in_progress|done --reason "..."` | Project Owner or elevated delegate required. Restores archived cards to an active state. |
+
+After `bootstrap`, find ids locally:
+
+- existing mission ids: `MyteCommandCenter/data/missions/*.yml` -> `mission_id`
+- suggestion ids: `MyteCommandCenter/data/mission-ops.yml` -> `queue[].suggestion_id` or `threads[].suggestion_id`
+- revise revision: `threads[].latest_revision` or `threads[].latest_server_revision.revision`
+- review revision: `threads[].review_revision`
+- thread type: `threads[].change_type`
+
 ## Feedback Action Map
 
 | Command | What It Does | Governance |
@@ -137,6 +221,8 @@ Mutation routes:
 - `POST /api/project-assistant/query`
 - `POST /api/project-assistant/run-qaqc`
 - `POST /api/project-assistant/mission-status-update`
+- `POST /api/project-assistant/mission-archive`
+- `POST /api/project-assistant/mission-restore`
 - `POST /api/project-assistant/project-comment`
 - `POST /api/project-assistant/update-owner`
 - `POST /api/project-assistant/client-update-drafts`

package/package.json

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