myte 0.0.22 → 0.0.24

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +84 -4
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -37,9 +37,22 @@ The CLI searches for `.env` in the current folder and then up parent directories
37
37
  - `npx myte bootstrap`
38
38
  - `npx myte sync-qaqc`
39
39
  - `npx myte feedback-sync`
40
+ - `npx myte feedback get --feedback-id <id>`
41
+ - `npx myte feedback history --feedback-id <id>`
40
42
  - `npx myte feedback status --feedback-id <id> --status in_review --reason "Ready for review"`
41
- - `npx myte feedback validate --file ./MyteCommandCenter/reviews/feedback/<id>-status.yml`
42
- - `npx myte feedback apply --file ./MyteCommandCenter/reviews/feedback/<id>-status.yml`
43
+ - `npx myte feedback edit --feedback-id <id> --title "Updated title" --feedback-text "Updated body" --reason "Clarify scope"`
44
+ - `npx myte feedback assign --feedback-id <id> --user-id <user_id> --reason "Assign to builder"`
45
+ - `npx myte feedback archive --feedback-id <id> --reason "Superseded"`
46
+ - `npx myte feedback validate --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
47
+ - `npx myte feedback submit --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
48
+ - `npx myte feedback reviews --status open`
49
+ - `npx myte feedback revise --request-id <id> --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
50
+ - `npx myte feedback review --request-id <id> --action approve --reason "Looks correct"`
51
+ - `npx myte feedback move --feedback-id <id> --to-state in_progress --reason "Started"`
52
+ - `npx myte feedback undo --feedback-id <id> --event-id <event_id> --reason "Undo accidental move"`
53
+ - `npx myte feedback prd-versions --feedback-id <id>`
54
+ - `npx myte feedback prd-diff --feedback-id <id> --version-id <version_id> --compare-to <base_version_id>`
55
+ - `npx myte feedback apply --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
43
56
  - `npx myte suggestions sync`
44
57
  - `npx myte query "Summarize the current branch changes" --with-diff`
45
58
  - `npx myte create-prd ./drafts/auth-prd.md`
@@ -50,7 +63,9 @@ The CLI searches for `.env` in the current folder and then up parent directories
50
63
  ## Behavior
51
64
 
52
65
  - `bootstrap`, `sync-qaqc`, `feedback-sync`, and `suggestions sync` write project-scoped local context under `MyteCommandCenter` in the current workspace unless `--output-dir` is provided.
53
- - `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.
66
+ - `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.
67
+ - `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.
68
+ - `feedback validate|apply` remains available for validation and owner-direct apply paths.
54
69
  - `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.
55
70
  - 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.
56
71
  - 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 +78,7 @@ The CLI searches for `.env` in the current folder and then up parent directories
63
78
  - `mission status`: update mission state
64
79
  - `sync-qaqc`: refresh active mission QAQC context locally
65
80
  - `feedback-sync`: refresh feedback and PRD context locally
66
- - `feedback status|edit|assign|archive|validate|apply|history|get`: create reviewable feedback refinement artifacts and apply them through the project-key API
81
+ - `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
67
82
  - `suggestions sync|create|revise|review`: work with mission suggestion workflow state
68
83
  - `query`: ask the project assistant, optionally with local diff context
69
84
  - `ai`: use the Myte AI gateway
@@ -74,3 +89,68 @@ The CLI searches for `.env` in the current folder and then up parent directories
74
89
 
75
90
  - The package ships the CLI only. Internal rollout notes, validation logs, and project-specific operating docs are not part of the public npm contract.
76
91
  - The public `myte` package is the supported entrypoint. The scoped `@mytegroupinc/myte-core` package is the implementation dependency used by the wrapper.
92
+
93
+ ## Feedback Action Map
94
+
95
+ | Command | What It Does | Governance |
96
+ | --- | --- | --- |
97
+ | `feedback-sync` | Pulls feedback metadata, comments, and PRD context into `MyteCommandCenter`. | Read-only project-key API call. |
98
+ | `feedback get` | Reads one feedback item's current server snapshot and `snapshot_hash`. | Read-only; backend checks project access. |
99
+ | `feedback status` | Creates a local YAML proposal to change canonical lifecycle state. | No live mutation until `submit` and owner/delegate review, except owner-direct `apply`. |
100
+ | `feedback edit` / `feedback refine` | Creates a local YAML proposal for title, description/body, priority, due date, tags, or notes. | Content changes go through owner-review membrane. |
101
+ | `feedback assign` | Creates a local YAML proposal to change assignee. | Goes through review unless applied through owner-direct path. |
102
+ | `feedback archive` | Creates a local YAML proposal to archive. | Archive is governed by backend owner/delegate capability. |
103
+ | `feedback submit` | Sends a local proposal artifact to the backend as a review request. | Does not mutate live feedback before approval. |
104
+ | `feedback revise` | Resubmits the original submitter's request after `request_changes`. | Only valid for the original submitter and `needs_changes` requests. |
105
+ | `feedback reviews` | Lists review requests or fetches one request by `--request-id`. | Read-only; response includes backend permissions. |
106
+ | `feedback review` | Approves, rejects, requests changes, or cancels a review request. | Backend restricts approval/review decisions to Project Owner or elevated delegate for Feedback scope. |
107
+ | `feedback move` | Moves a card across allowed board states directly with an audit event. | Safe states are direct; governed states such as archive/reject/deploy remain backend-authorized. |
108
+ | `feedback undo` | Reverses an audited board event when there is no conflict. | Backend validates event ownership/project scope and conflict state. |
109
+ | `feedback prd-versions` | Lists retained PRD baselines/revisions for a feedback item. | Read-only; old S3 objects are retained by reference. |
110
+ | `feedback prd-diff` | Fetches backend-generated text diff for PRD versions. | Read-only; backend controls version access. |
111
+ | `feedback history` | Lists audited feedback board/refinement events. | Read-only; backend checks project access. |
112
+ | `feedback validate` | Sends an artifact to backend validation without mutation. | Useful before submit or owner-direct apply. |
113
+ | `feedback apply` | Applies an artifact through the owner-direct/emergency path. | Not the normal collaborator flow; normal flow is `submit` -> `review`. |
114
+
115
+ ## Direct Project API Surface
116
+
117
+ All routes use `Authorization: Bearer <MYTE_API_KEY>`. The CLI adds idempotency and client-session headers on mutation routes.
118
+
119
+ Read/sync routes:
120
+
121
+ - `GET /api/project-assistant/config`
122
+ - `GET /api/project-assistant/bootstrap`
123
+ - `GET /api/project-assistant/qaqc-sync`
124
+ - `GET /api/project-assistant/feedback-sync`
125
+ - `GET /api/project-assistant/feedback/<feedback_id>`
126
+ - `GET /api/project-assistant/feedback/<feedback_id>/refinement/history`
127
+ - `GET /api/project-assistant/feedback-review-requests`
128
+ - `GET /api/project-assistant/feedback-review-requests/<request_id>`
129
+ - `GET /api/project-assistant/feedback/<feedback_id>/events`
130
+ - `GET /api/project-assistant/feedback/<feedback_id>/prd/versions`
131
+ - `GET /api/project-assistant/feedback/<feedback_id>/prd/versions/<version_id>/diff`
132
+ - `GET /api/project-assistant/suggestions`
133
+ - `GET /api/project-assistant/run-qaqc/<batch_id>`
134
+
135
+ Mutation routes:
136
+
137
+ - `POST /api/project-assistant/query`
138
+ - `POST /api/project-assistant/run-qaqc`
139
+ - `POST /api/project-assistant/mission-status-update`
140
+ - `POST /api/project-assistant/project-comment`
141
+ - `POST /api/project-assistant/update-owner`
142
+ - `POST /api/project-assistant/client-update-drafts`
143
+ - `POST /api/project-assistant/create-prd`
144
+ - `POST /api/project-assistant/create-prds`
145
+ - `POST /api/project-assistant/feedback/<feedback_id>/refinement/validate`
146
+ - `POST /api/project-assistant/feedback/<feedback_id>/refinement/requests`
147
+ - `POST /api/project-assistant/feedback-review-requests/<request_id>/revise`
148
+ - `POST /api/project-assistant/feedback/<feedback_id>/refinement/apply`
149
+ - `POST /api/project-assistant/feedback-review-requests/<request_id>/review`
150
+ - `POST /api/project-assistant/feedback-review-requests/<request_id>/request-changes`
151
+ - `POST /api/project-assistant/feedback-review-requests/<request_id>/cancel`
152
+ - `POST /api/project-assistant/feedback/<feedback_id>/board-move`
153
+ - `POST /api/project-assistant/feedback/<feedback_id>/events/<event_id>/undo`
154
+ - `POST /api/project-assistant/suggestions`
155
+ - `POST /api/project-assistant/suggestions/revise`
156
+ - `POST /api/project-assistant/suggestions/review`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "myte",
3
- "version": "0.0.22",
3
+ "version": "0.0.24",
4
4
  "description": "Myte developer CLI.",
5
5
  "type": "commonjs",
6
6
  "license": "MIT",
@@ -16,6 +16,6 @@
16
16
  "node": ">=18"
17
17
  },
18
18
  "dependencies": {
19
- "@mytegroupinc/myte-core": "0.0.22"
19
+ "@mytegroupinc/myte-core": "0.0.24"
20
20
  }
21
21
  }