myte 0.0.21 → 0.0.23

package/README.md

@@ -38,6 +38,10 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `npx myte sync-qaqc`
 - `npx myte feedback-sync`
 - `npx myte feedback status --feedback-id <id> --status in_review --reason "Ready for review"`
+- `npx myte feedback submit --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
+- `npx myte feedback reviews --status open`
+- `npx myte feedback review --request-id <id> --action approve --reason "Looks correct"`
+- `npx myte feedback move --feedback-id <id> --to-state in_progress --reason "Started"`
 - `npx myte feedback validate --file ./MyteCommandCenter/reviews/feedback/<id>-status.yml`
 - `npx myte feedback apply --file ./MyteCommandCenter/reviews/feedback/<id>-status.yml`
 - `npx myte suggestions sync`
@@ -50,7 +54,9 @@ 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.
-- `feedback status|edit|assign|archive` writes local review artifacts under `MyteCommandCenter/reviews/feedback`; `feedback validate|apply` sends those artifacts to the backend, where authorization, stale snapshot checks, allowed transitions, and history are enforced.
+- `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.
 - `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.
 - 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.
@@ -63,7 +69,7 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `mission status`: update mission state
 - `sync-qaqc`: refresh active mission QAQC context locally
 - `feedback-sync`: refresh feedback and PRD context locally
-- `feedback status|edit|assign|archive|validate|apply|history|get`: create reviewable feedback refinement artifacts and apply them through the project-key API
+- `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

package/package.json

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