myte 0.0.26 → 0.0.28

package/README.md

@@ -56,7 +56,6 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `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."`
@@ -67,7 +66,8 @@ The CLI searches for `.env` in the current folder and then up parent directories
 
 - `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.
+- `mission status` is active-state only (`todo`, `in_progress`, `done`). Use `mission archive` for project-key lifecycle archival; restore archived missions from the web archived-board view.
+- `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 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.
@@ -94,7 +94,7 @@ Recommended agent flow:
 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.
+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`.
 
 PRD document contract:
@@ -137,7 +137,6 @@ Feedback comments nuance:
 - `run-qaqc`: queue QAQC for explicit mission ids
 - `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
@@ -162,9 +161,8 @@ Feedback comments nuance:
 | 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. |
+| Update mission status | `myte mission status --mission-ids "M001" --status todo|in_progress|done` | Active status update only; refreshes local bootstrap + mission-ops by default. |
+| Archive mission | `myte mission archive --mission-ids "M001" --reason "..."` | Project Owner or elevated delegate required. Keeps the mission record, hides it from normal board/bootstrap state, and refreshes local bootstrap + mission-ops by default. |
 
 After `bootstrap`, find ids locally:
 
@@ -222,7 +220,6 @@ Mutation routes:
 - `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.26",
+  "version": "0.0.28",
   "description": "Myte developer CLI.",
   "type": "commonjs",
   "license": "MIT",
@@ -16,6 +16,6 @@
     "node": ">=18"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.26"
+    "@mytegroupinc/myte-core": "0.0.28"
   }
 }