myte 0.0.57 → 0.0.58

package/README.md

@@ -104,10 +104,10 @@ The CLI searches for `.env` in the current folder and then up parent directories
   guidance and add bounded jitter to prevent synchronized IDE poll bursts.
 - Owner updates are accepted into a durable delivery outbox; a successful CLI
   response means the update was queued, while delivery status remains server-owned.
-- `bootstrap`, `sync-qaqc`, `feedback-sync`, and `suggestions sync` write project-scoped local context under `MyteCommandCenter` in the current workspace unless `--output-dir` is provided.
-- Successful commands perform a cached, best-effort check for a newer `myte` package version. Notices are advisory, go to `stderr`, and do not break commands or JSON stdout. Disable with `--no-update-check` or `MYTE_PACKAGE_UPDATE_CHECK=0`.
-- `bootstrap` writes mission cards and mission suggestion thread state together; agents should run it before looking for mission or suggestion ids.
-- `build verify --json` is read-only. It checks that every active mission in the last bootstrap has a readable terminal QA/QC summary with no failed or pending cases, but it does not run QA/QC, repository tests, or semantic review.
+- `bootstrap`, `sync-qaqc`, `feedback-sync`, and `suggestions sync` write project-scoped local context under `MyteCommandCenter` in the current workspace unless `--output-dir` is provided.
+- Successful commands perform a cached, best-effort check for a newer `myte` package version. Notices are advisory, go to `stderr`, and do not break commands or JSON stdout. Disable with `--no-update-check` or `MYTE_PACKAGE_UPDATE_CHECK=0`.
+- `bootstrap` writes mission cards and mission suggestion thread state together; agents should run it before looking for mission or suggestion ids.
+- `build verify --json` is read-only. It checks that every active mission in the last bootstrap has a readable terminal QA/QC summary with no failed or pending cases, but it does not run QA/QC, repository tests, or semantic review.
 - `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.
 - `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.
 - `feedback status|edit|assign|archive|refine` writes local review artifacts under `MyteCommandCenter/reviews/feedback`.
@@ -206,11 +206,11 @@ PRD document contract:
 - Renderer-friendly PRDs should use one `# Title`, `##` sections, concise paragraphs, bullets, GitHub tables/checklists where useful, and fenced code blocks only for real code/config.
 - Do not wrap the whole PRD in a ` ```markdown ` fence. Do not use raw HTML, inline style blocks, or decorative banners.
 - PRD identity is explicit: `myte create-prd` creates a PRD asset with PRD metadata. Generic uploaded `.md`, `.docx`, `.pdf`, and `.txt` files remain normal attachments unless explicitly created as PRDs.
-- Document-set uploads preserve the exact source Markdown and also store a
-  normalized rendering copy. Rendering cleanup never silently rewrites the
-  approved source.
-- Every newly created PRD receives immutable version `1` and a stable primary document id. Creation responses return `active_prd_version_id`, `active_prd_version_number`, and `primary_document_id`, which can be passed directly into `feedback tickets create`.
-- A sub-ticket may link at most 25 PRD documents, and the backend rejects any version/document pair that does not belong to that exact Feedback/PRD before mutation.
+- Document-set uploads preserve the exact source Markdown and also store a
+  normalized rendering copy. Rendering cleanup never silently rewrites the
+  approved source.
+- Every newly created PRD receives immutable version `1` and a stable primary document id. Creation responses return `active_prd_version_id`, `active_prd_version_number`, and `primary_document_id`, which can be passed directly into `feedback tickets create`.
+- A sub-ticket may link at most 25 PRD documents, and the backend rejects any version/document pair that does not belong to that exact Feedback/PRD before mutation.
 
 ## Connectivity Diagnostics
 
@@ -227,14 +227,14 @@ Interpret the first failed layer:
 - `tls`: the secure connection was reset or certificate validation failed
   before an HTTP request reached Myte.
 - `http`: Myte or an intermediary returned a status or non-JSON response.
-- `authentication` / `authorization`: the API received the request and
-  rejected the credential or capability.
-
-An authorization response with `policy_consent_required` means the key is
-valid, but the user who created it must review and accept the current Myte
-Policy from the mission-board link printed by the CLI. Rotate the key only if
-the API reports authentication failure or revocation; policy acceptance is a
-separate user-governance step.
+- `authentication` / `authorization`: the API received the request and
+  rejected the credential or capability.
+
+An authorization response with `policy_consent_required` means the key is
+valid, but the user who created it must review and accept the current Myte
+Policy from the mission-board link printed by the CLI. Rotate the key only if
+the API reports authentication failure or revocation; policy acceptance is a
+separate user-governance step.
 
 On restricted Wi-Fi, complete any captive-portal login, configure the
 network's supported proxy/VPN, or retry on another network. The CLI honors
@@ -295,9 +295,9 @@ Feedback comments nuance:
   package version. `mytecody update` updates the engine only. Use
   `npm install -g myte@latest` to update the launcher and the Myte API CLI
   commands shipped by npm.
-- `create-prd`: upload deterministic PRD markdown as the stored renderable PRD document; use `description` only as the short card summary
-- `update-team`, `update-owner`, `update-client`: send project updates through the project-key surface
-- Successful `myte` commands check the npm registry at most once per day for a newer package version. Notices are advisory, go to `stderr`, and never block the command. Use `--no-update-check` or `MYTE_PACKAGE_UPDATE_CHECK=0` to disable them.
+- `create-prd`: upload deterministic PRD markdown as the stored renderable PRD document; use `description` only as the short card summary
+- `update-team`, `update-owner`, `update-client`: send project updates through the project-key surface
+- Successful `myte` commands check the npm registry at most once per day for a newer package version. Notices are advisory, go to `stderr`, and never block the command. Use `--no-update-check` or `MYTE_PACKAGE_UPDATE_CHECK=0` to disable them.
 
 ## Notes
 

package/package.json

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