myte 0.0.56 → 0.0.57

package/README.md

@@ -104,8 +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.
-- `bootstrap` writes mission cards and mission suggestion thread state together; agents should run it before looking for mission or suggestion ids.
+- `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`.
@@ -293,8 +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
+- `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.56",
+  "version": "0.0.57",
   "description": "Myte developer CLI.",
   "type": "commonjs",
   "license": "MIT",
@@ -19,6 +19,6 @@
     "node": ">=18.17"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.56"
+    "@mytegroupinc/myte-core": "0.0.57"
   }
 }