myte 0.0.43 → 0.0.44

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 +37 -30
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -33,9 +33,11 @@ No install:
33
33
 
34
34
  The CLI searches for `.env` in the current folder and then up parent directories.
35
35
 
36
- ## Common Commands
37
-
38
- - `npx myte config --json`
36
+ ## Common Commands
37
+
38
+ Live mutation commands require `--confirm-write --approval-artifact <path>` after the local artifact has been shown to and approved by the user.
39
+
40
+ - `npx myte config --json`
39
41
  - `npx myte bootstrap`
40
42
  - `npx myte sync-qaqc`
41
43
  - `npx myte feedback-sync`
@@ -70,10 +72,11 @@ The CLI searches for `.env` in the current folder and then up parent directories
70
72
  - `npx mytecody update --dry-run`
71
73
  - `npx mytecody update`
72
74
 
73
- ## Behavior
74
-
75
- - `bootstrap`, `sync-qaqc`, `feedback-sync`, and `suggestions sync` write project-scoped local context under `MyteCommandCenter` in the current workspace unless `--output-dir` is provided.
76
- - `bootstrap` writes mission cards and mission suggestion thread state together; agents should run it before looking for mission or suggestion ids.
75
+ ## Behavior
76
+
77
+ - `bootstrap`, `sync-qaqc`, `feedback-sync`, and `suggestions sync` write project-scoped local context under `MyteCommandCenter` in the current workspace unless `--output-dir` is provided.
78
+ - Live project-key mutations require explicit user approval before the CLI sends them. Create a local approval artifact, show it to the user, then rerun with `--confirm-write --approval-artifact <path>`.
79
+ - `bootstrap` writes mission cards and mission suggestion thread state together; agents should run it before looking for mission or suggestion ids.
77
80
  - `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.
78
81
  - `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.
79
82
  - `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.
@@ -96,17 +99,21 @@ MYTE_API_KEY=<project_api_key>
96
99
 
97
100
  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.
98
101
 
99
- Recommended agent flow:
100
-
101
- 1. Run `myte config --json` to confirm the project, API base, configured repos, and local workspace detection.
102
- 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.
103
- 3. Use `myte query "<goal/evidence/ask>" --with-diff` when local code changes matter.
104
- 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.
105
- 5. Use `myte feedback status|edit|assign|archive` to create reviewable local artifacts, then `feedback submit` and `feedback review` for the owner-review membrane.
106
- 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.
107
- 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`.
108
- 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.
109
- 9. Use `myte update-team "<content>"` for project/team comments through `/api/project-assistant/project-comment`, and `myte feedback comment --feedback-id <id> --body-file ./comment.md` for feedback-specific implementation notes.
102
+ Recommended agent flow:
103
+
104
+ 1. Run `myte config --json` to confirm the project, API base, configured repos, and local workspace detection.
105
+ 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.
106
+ 3. Use `myte query "<goal/evidence/ask>" --with-diff` when local code changes matter.
107
+ 4. Before any live write, create a local approval artifact, show it to the user, and get explicit approval. Use `.md` for comments, human updates, and PRD markdown; use `.yml`/`.yaml` or `.json` for structured mission/feedback decisions and batch writes.
108
+ 5. After approval, rerun the mutation with `--confirm-write --approval-artifact <path>`. Batch artifacts must enumerate every feedback id, mission id, suggestion id, request id, or PRD item.
109
+ 6. Direct HTTP calls with `MYTE_API_KEY` cannot bypass this gate on live project-content mutations. The API returns `428` with agent instructions when approval metadata is missing or mismatched.
110
+ 7. Read/sync/query/validate commands, `--print-context`, and `--dry-run` do not require write approval.
111
+ 8. 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.
112
+ 9. Use `myte feedback status|edit|assign|archive` to create reviewable local artifacts, then `feedback submit` and `feedback review` for the owner-review membrane.
113
+ 10. 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.
114
+ 11. 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`.
115
+ 12. 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.
116
+ 13. Use `myte update-team "<content>"` for project/team comments through `/api/project-assistant/project-comment`, and `myte feedback comment --feedback-id <id> --body-file ./comment.md` for feedback-specific implementation notes.
110
117
 
111
118
  PRD document contract:
112
119
 
@@ -241,7 +248,7 @@ The harness creates five disposable `TEST` feedback items from markdown, verifie
241
248
 
242
249
  ## Direct Project API Surface
243
250
 
244
- All routes use `Authorization: Bearer <MYTE_API_KEY>`. The CLI adds idempotency and client-session headers on mutation routes.
251
+ All routes use `Authorization: Bearer <MYTE_API_KEY>`. The CLI adds idempotency and client-session headers on mutation routes. Live project-content mutation routes also require write-approval headers; the official CLI supplies them from `--confirm-write --approval-artifact <path>`.
245
252
 
246
253
  Read/sync routes:
247
254
 
@@ -256,22 +263,22 @@ Read/sync routes:
256
263
  - `GET /api/project-assistant/feedback/<feedback_id>/events`
257
264
  - `GET /api/project-assistant/feedback/<feedback_id>/prd/versions`
258
265
  - `GET /api/project-assistant/feedback/<feedback_id>/prd/versions/<version_id>/diff`
259
- - `GET /api/project-assistant/suggestions`
260
- - `GET /api/project-assistant/run-qaqc/<batch_id>`
261
-
262
- Mutation routes:
263
-
264
- - `POST /api/project-assistant/query`
265
- - `POST /api/project-assistant/run-qaqc`
266
+ - `GET /api/project-assistant/suggestions`
267
+ - `GET /api/project-assistant/run-qaqc/<batch_id>`
268
+ - `POST /api/project-assistant/query`
269
+ - `POST /api/project-assistant/feedback/<feedback_id>/refinement/validate`
270
+
271
+ Live project-content mutation routes:
272
+
273
+ - `POST /api/project-assistant/run-qaqc`
266
274
  - `POST /api/project-assistant/mission-status-update`
267
275
  - `POST /api/project-assistant/mission-archive`
268
276
  - `POST /api/project-assistant/project-comment`
269
277
  - `POST /api/project-assistant/update-owner`
270
278
  - `POST /api/project-assistant/client-update-drafts`
271
- - `POST /api/project-assistant/create-prd`
272
- - `POST /api/project-assistant/create-prds`
273
- - `POST /api/project-assistant/feedback/<feedback_id>/refinement/validate`
274
- - `POST /api/project-assistant/feedback/<feedback_id>/refinement/requests`
279
+ - `POST /api/project-assistant/create-prd`
280
+ - `POST /api/project-assistant/create-prds`
281
+ - `POST /api/project-assistant/feedback/<feedback_id>/refinement/requests`
275
282
  - `POST /api/project-assistant/feedback-review-requests/<request_id>/revise`
276
283
  - `POST /api/project-assistant/feedback/<feedback_id>/refinement/apply`
277
284
  - `POST /api/project-assistant/feedback-review-requests/<request_id>/review`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "myte",
3
- "version": "0.0.43",
3
+ "version": "0.0.44",
4
4
  "description": "Myte developer CLI.",
5
5
  "type": "commonjs",
6
6
  "license": "MIT",
@@ -19,6 +19,6 @@
19
19
  "node": ">=18"
20
20
  },
21
21
  "dependencies": {
22
- "@mytegroupinc/myte-core": "0.0.43"
22
+ "@mytegroupinc/myte-core": "0.0.44"
23
23
  }
24
24
  }