myte 0.0.52 → 0.0.54

package/README.md

@@ -53,7 +53,8 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `npx myte feedback get --feedback-id <id>`
 - `npx myte feedback history --feedback-id <id>`
 - `npx myte feedback status --feedback-id <id> --status in_review --reason "Ready for review"`
-- `npx myte feedback edit --feedback-id <id> --title "Updated title" --feedback-text "Updated body" --reason "Clarify scope"`
+- `npx myte feedback edit --feedback-id <id> --title "Updated title" --feedback-text "Updated body" --reason "Clarify scope"`
+- `npx myte feedback document-add --feedback-id <id> --prd-file ./docs/linked-addendum.md --title "Linked PRD addendum" --reason "Extend governed Feedback context"`
 - `npx myte feedback assign --feedback-id <id> --user-id <user_id> --reason "Assign to builder"`
 - `npx myte feedback archive --feedback-id <id> --reason "Superseded"`
 - `npx myte feedback validate --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
@@ -73,6 +74,7 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `npx myte mission archive --mission-ids "M001" --reason "Duplicate disposable mission"`
 - `npx myte query "Summarize the current branch changes" --with-diff --json`
 - `npx myte create-prd ./drafts/auth-prd.md --confirm-write --approval-artifact ./drafts/auth-prd.md`
+- `npx myte create-prd ./drafts/auth-prd.md --assigned-user-email dev@example.com --confirm-write --approval-artifact ./drafts/auth-prd.md`
 - `npx myte create-prd ./drafts/proposal.md ./drafts/harness.md ./drafts/security.md --document-set --confirm-write --approval-artifact ./drafts/approval.md`
 - `npx myte update-team "Backend deploy completed." --confirm-write --approval-artifact ./updates/team.md`
 - `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md --confirm-write --approval-artifact ./updates/owner.md`
@@ -170,7 +172,7 @@ 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`. `bootstrap` also writes `MyteCommandCenter/AgentsMyteAPI.md`, the local action matrix agents should consult before mutating Myte state. 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> --confirm-write --approval-artifact <path>` only after the PRD markdown has been reviewed by a human. Add `--document-set` for one parent with up to three ordered documents. Without that flag, multiple files remain independent PRDs. The file body is the PRD document; `--description` is only the short board/card summary.
+4. Use `myte create-prd <file.md> --confirm-write --approval-artifact <path>` only after the PRD markdown has been reviewed by a human. Add `--document-set` for one parent with up to three ordered documents. Without that flag, multiple files remain independent PRDs. The file body is the PRD document; `--description` is only the short board/card summary. New PRDs are unassigned by default; add `--assigned-user-id <id>` or `--assigned-user-email <exact-email>` to assign an eligible project user atomically during creation.
 5. Use `myte feedback status|edit|assign|archive|refine` to create reviewable local artifacts. `feedback submit` and `feedback revise` require an approval artifact; `feedback review` does not because the backend owner/delegate review membrane is the approval control.
 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. `suggestions create` and `suggestions revise` require an approval artifact; `suggestions review` does not because the backend Project Owner/elevated-delegate decision is the approval control. Valid create `change_type` values are exactly `update` and `create`; revisions keep the existing thread type and must not include `change_type`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "myte",
-  "version": "0.0.52",
+  "version": "0.0.54",
   "description": "Myte developer CLI.",
   "type": "commonjs",
   "license": "MIT",
@@ -19,6 +19,6 @@
     "node": ">=18.17"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.52"
+    "@mytegroupinc/myte-core": "0.0.54"
   }
 }