@mytegroupinc/myte-core 0.0.8 → 0.0.10
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.
- package/README.md +55 -9
- package/cli.js +1699 -187
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,28 +4,44 @@ Internal implementation package for the `myte` CLI.
|
|
|
4
4
|
|
|
5
5
|
Most users should install the unscoped wrapper instead:
|
|
6
6
|
- `npm install myte` then `npx myte bootstrap`
|
|
7
|
+
- `npm install myte` then `npx myte run-qaqc --mission-ids M001 --wait --sync`
|
|
7
8
|
- `npm install myte` then `npx myte sync-qaqc`
|
|
8
9
|
- `npm install myte` then `npx myte feedback-sync`
|
|
10
|
+
- `npm install myte` then `npx myte suggestions sync`
|
|
11
|
+
- `npm install myte` then `npx myte suggestions create`
|
|
12
|
+
- `npm install myte` then `npx myte suggestions revise`
|
|
13
|
+
- `npm install myte` then `npx myte suggestions review`
|
|
9
14
|
- `npm install myte` then `npx myte query "..." --with-diff`
|
|
10
15
|
- `npm install myte` then `npm exec myte -- query "..." --with-diff`
|
|
11
16
|
- `npm install myte` then `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
|
|
12
17
|
- `npm install myte` then `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
|
|
13
18
|
- `npm install myte` then `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
|
|
14
19
|
- `npm i -g myte` then `myte bootstrap`
|
|
20
|
+
- `npm i -g myte` then `myte run-qaqc --mission-ids M001 --wait --sync`
|
|
15
21
|
- `npm i -g myte` then `myte sync-qaqc`
|
|
16
22
|
- `npm i -g myte` then `myte feedback-sync`
|
|
23
|
+
- `npm i -g myte` then `myte suggestions sync`
|
|
24
|
+
- `npm i -g myte` then `myte suggestions create`
|
|
25
|
+
- `npm i -g myte` then `myte suggestions revise`
|
|
26
|
+
- `npm i -g myte` then `myte suggestions review`
|
|
17
27
|
- `npm i -g myte` then `myte query "..." --with-diff`
|
|
18
28
|
- `npm i -g myte` then `myte update-team "Backend deploy completed; QAQC rerun queued."`
|
|
19
29
|
- `npm i -g myte` then `myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
|
|
20
30
|
- `npm i -g myte` then `myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
|
|
21
31
|
- `npx myte@latest bootstrap`
|
|
32
|
+
- `npx myte@latest run-qaqc --mission-ids M001 --wait --sync`
|
|
22
33
|
- `npx myte@latest sync-qaqc`
|
|
23
34
|
- `npx myte@latest feedback-sync`
|
|
35
|
+
- `npx myte@latest suggestions sync`
|
|
36
|
+
- `npx myte@latest suggestions create`
|
|
37
|
+
- `npx myte@latest suggestions revise`
|
|
38
|
+
- `npx myte@latest suggestions review`
|
|
24
39
|
- `npx myte@latest query "..." --with-diff`
|
|
25
40
|
- `npx myte@latest update-team "Backend deploy completed; QAQC rerun queued."`
|
|
26
41
|
- `npx myte@latest update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
|
|
27
42
|
- `npx myte@latest update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
|
|
28
43
|
- `npm install myte` then `npx myte create-prd ./drafts/auth-prd.md`
|
|
44
|
+
- `npm install myte` then `npx myte create-prd ./drafts/auth-prd.md ./drafts/billing-prd.md`
|
|
29
45
|
- `cat ./drafts/auth-prd.md | npx myte create-prd --stdin`
|
|
30
46
|
|
|
31
47
|
Requirements:
|
|
@@ -40,17 +56,39 @@ Notes:
|
|
|
40
56
|
- `npm install myte` means the CLI is available locally; bare `myte ...` still requires a global install.
|
|
41
57
|
- `bootstrap` is a local file materialization path, not a hosted file download.
|
|
42
58
|
- `bootstrap` expects to run from a wrapper root that contains the project's configured repo folders.
|
|
43
|
-
- `bootstrap` writes `MyteCommandCenter/data/phases`, `epics`, `stories`,
|
|
59
|
+
- `bootstrap` writes `MyteCommandCenter/data/project.yml` plus itemized `phases`, `epics`, `stories`, and `missions`.
|
|
44
60
|
- `bootstrap` materializes a public Command Center DTO, not raw backend documents.
|
|
61
|
+
- `bootstrap` mission cards now include richer execution context like `complexity`, `estimated_hours`, `due_date`, `subtasks`, `technical_requirements`, `resources_needed`, `labels`, and normalized `test_cases`.
|
|
45
62
|
- `bootstrap` excludes internal keys like `_id`, `org_id`, `project_id`, `created_by`, `assigned_to`, and raw `qa_qc_results`.
|
|
46
|
-
-
|
|
47
|
-
- `
|
|
63
|
+
- rerunning current commands on an older workspace automatically prunes legacy artifacts like `bootstrap-manifest.json`, `data/qaqc/`, and `data/feedback/` as the new files are written.
|
|
64
|
+
- `run-qaqc` queues QAQC for up to 10 explicit mission ids through `/api/project-assistant/run-qaqc`.
|
|
65
|
+
- `run-qaqc --wait` polls `/api/project-assistant/run-qaqc/<batch_id>` until the batch is terminal.
|
|
66
|
+
- `run-qaqc --sync` refreshes `MyteCommandCenter/data/qaqc.yml` after a completed batch.
|
|
67
|
+
- project-key QAQC runs through the dedicated `project_api_qaqc` queue inside the existing Celery service, with a global budget of `20` dispatch starts/minute and `20` live jobs.
|
|
68
|
+
- a saturated `run-qaqc --wait` batch can take roughly `5-10` minutes before `--sync` has final data to write.
|
|
69
|
+
- `sync-qaqc` works without `bootstrap`; it creates `MyteCommandCenter/data/qaqc.yml` automatically if missing.
|
|
70
|
+
- `sync-qaqc` writes the active mission QAQC working set to `MyteCommandCenter/data/qaqc.yml`.
|
|
48
71
|
- `sync-qaqc` only exports active `Todo` / `In Progress` missions plus a public QAQC summary and sanitized latest batch metadata.
|
|
49
|
-
- `sync-qaqc`
|
|
50
|
-
- `
|
|
51
|
-
- `feedback-sync` writes
|
|
52
|
-
- `feedback-sync`
|
|
53
|
-
- `
|
|
72
|
+
- `sync-qaqc` keeps QAQC state in one deterministic file so the working set grows and shrinks with current active-mission reality.
|
|
73
|
+
- `sync-qaqc` fully rewrites `MyteCommandCenter/data/qaqc.yml` on every sync and does not delete `MyteCommandCenter/data/missions/*.yml`.
|
|
74
|
+
- `feedback-sync` writes one deterministic feedback snapshot under `MyteCommandCenter/data/feedback.yml`.
|
|
75
|
+
- `feedback-sync` includes readable PRD text inline when PRD text exists.
|
|
76
|
+
- `feedback-sync` fully replaces the feedback-owned sync file to avoid stale local feedback noise.
|
|
77
|
+
- `feedback-sync` fully rewrites `MyteCommandCenter/data/feedback.yml` on every sync and does not delete `MyteCommandCenter/data/missions/*.yml`.
|
|
78
|
+
- `suggestions sync` writes one merge-safe workflow file at `MyteCommandCenter/data/mission-ops.yml`.
|
|
79
|
+
- `suggestions sync` should be the first step before ideating locally so new submissions start from the latest aggregated thread state.
|
|
80
|
+
- `suggestions sync` rewrites the canonical synced state into `threads[]` and preserves top-level `workspace.<actor_scope>` blocks plus per-thread `workspace.<actor_scope>` drafts from the existing file.
|
|
81
|
+
- synced `threads[]` include aggregate diffs, conflict summaries, and archived decision lineage so local agents do not need to reconstruct review state.
|
|
82
|
+
- `suggestions create` reads a structured file payload or local `workspace.<actor_scope>.draft_submissions[]` blocks from `mission-ops.yml`.
|
|
83
|
+
- `suggestions revise` reads structured file payloads or local per-thread `workspace.<actor_scope>` drafts only when `draft_status` is `submit`, `ready`, or `pending_submit`.
|
|
84
|
+
- `suggestions review` is owner-only, reads structured file payloads or local per-thread owner review intent, and refreshes `data/missions/*.yml` when approvals apply changes.
|
|
85
|
+
- `suggestions review` requires an explicit `review_action` of `request_changes`, `approve`, or `reject`; there is no persisted save-draft review action.
|
|
86
|
+
- suggestion notifications deep-link into the project Reviews workspace for the affected thread.
|
|
87
|
+
- create/revise/review resync `mission-ops.yml` by default unless `--no-sync` is passed.
|
|
88
|
+
- create/revise/review automatically send `X-Idempotency-Key` and a default `client_session_id` so retries stay deterministic and auditable.
|
|
89
|
+
- `--print-context` prints the JSON payload that would be submitted for create/revise/review.
|
|
90
|
+
- `mission-ops.yml` keeps synced thread lineage plus actor-local draft space in one file; terminal items fall out of `queue` after sync but remain in `threads[]`.
|
|
91
|
+
- `create-prd` is the deterministic PRD upload path, not an LLM generation command.
|
|
54
92
|
- `update-team` creates a project comment through `/api/project-assistant/project-comment`.
|
|
55
93
|
- `update-owner` sends a direct owner email through `/api/project-assistant/update-owner`.
|
|
56
94
|
- `update-owner` requires `--subject` plus body markdown from `--body-markdown`, `--body-file`, positional input, or `--stdin`.
|
|
@@ -66,19 +104,27 @@ Notes:
|
|
|
66
104
|
|
|
67
105
|
Deterministic `create-prd` contract:
|
|
68
106
|
- Required: `MYTE_API_KEY`, a PRD markdown body, and a title.
|
|
107
|
+
- Accepts one file or many files per command. The CLI uses `/project-assistant/create-prd` for one item and automatically uses the batch upload path for multi-file requests.
|
|
69
108
|
- Title source: `myte-kanban.title`, the first markdown `# Heading`, or `--title`.
|
|
70
109
|
- Description source: `myte-kanban.description` or `--description`.
|
|
71
|
-
- The markdown body is stored verbatim as PRD content and is what the backend uses to build the PRD DOCX.
|
|
110
|
+
- The markdown body (`prd_markdown`, or the body portion of `ticket_markdown`) is stored verbatim as PRD content and is what the backend uses to build the PRD DOCX.
|
|
72
111
|
- Legacy `feedback_text` is still accepted for older payloads, but new callers should use `description`.
|
|
73
112
|
- Optional structured fields: `priority`, `status`, `tags`, `assigned_user_email`, `assigned_user_id`, `due_date`, `repo_name`, `repo_id`, `preview_url`, `source`.
|
|
74
113
|
|
|
75
114
|
Examples:
|
|
76
115
|
- `npx myte bootstrap`
|
|
116
|
+
- `npx myte run-qaqc --mission-ids M001,M002 --wait --sync`
|
|
77
117
|
- `npx myte sync-qaqc`
|
|
78
118
|
- `npx myte feedback-sync`
|
|
119
|
+
- `npx myte suggestions sync`
|
|
120
|
+
- `npx myte suggestions create --file ./changes/create.yml`
|
|
121
|
+
- `npx myte suggestions create`
|
|
122
|
+
- `npx myte suggestions revise`
|
|
123
|
+
- `npx myte suggestions review`
|
|
79
124
|
- `npx myte bootstrap --dry-run --json`
|
|
80
125
|
- `npx myte sync-qaqc --dry-run --json`
|
|
81
126
|
- `npx myte create-prd ./drafts/auth-prd.md --description "Short card summary"`
|
|
127
|
+
- `npx myte create-prd ./drafts/auth-prd.md ./drafts/billing-prd.md`
|
|
82
128
|
- `npx myte create-prd ./drafts/auth-prd.md --print-context`
|
|
83
129
|
- `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
|
|
84
130
|
- `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md`
|