myte 0.0.55 → 0.0.57

package/README.md

@@ -66,6 +66,9 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `npx myte feedback move --feedback-id <id> --to-state in_progress --reason "Started"`
 - `npx myte feedback move --feedback-ids "<id1,id2>" --to-state in_progress --reason "Batch move"`
 - `npx myte feedback comment --feedback-id <id> --body-file ./updates/feedback-comment.md --confirm-write --approval-artifact ./updates/feedback-comment.md`
+- `npx myte feedback tickets list --feedback-id <id> --json`
+- `npx myte feedback tickets create --feedback-id <id> --file ./tickets.json --dry-run --json`
+- `npx myte feedback tickets update --feedback-id <id> --ticket-ids "<id1,id2>" --status in_progress --confirm-write --approval-artifact ./ticket-update.yml --json`
 - `npx myte feedback undo --feedback-id <id> --event-id <event_id> --reason "Undo accidental move"`
 - `npx myte feedback prd-versions --feedback-id <id>`
 - `npx myte feedback prd-diff --feedback-id <id> --version-id <version_id> --compare-to <base_version_id>`
@@ -94,21 +97,23 @@ The CLI searches for `.env` in the current folder and then up parent directories
   portal/non-JSON, authentication, authorization, rate-limit, and server
   response failures. Do not disable TLS verification to work around a failed
   diagnostic.
-- Safe transient reads and query polling use bounded retries. Query creation
-  uses one stable idempotency key across ambiguous retries so a lost response
-  cannot create duplicate inference jobs.
-- Query and QAQC polling honor server `Retry-After` / `next_poll_after_ms`
-  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.
+- Safe transient reads and query polling use bounded retries. Query creation
+  uses one stable idempotency key across ambiguous retries so a lost response
+  cannot create duplicate inference jobs.
+- Query and QAQC polling honor server `Retry-After` / `next_poll_after_ms`
+  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.
 - `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`.
 - `feedback submit|revise|comment` are live writes that require `--confirm-write --approval-artifact <path>`.
 - `feedback review|move|undo|apply` are governed writes with backend permission checks but no approval artifact flags.
-- `feedback-sync|get|history|reviews|prd-versions|prd-diff|validate` are read/sync/validation commands with no approval artifact flags.
+- `feedback-sync|get|history|reviews|prd-versions|prd-diff|validate` and `feedback tickets list|validate-create|validate-update` are read/sync/validation commands with no approval artifact flags.
 - `feedback review --request-ids` sends one backend batch review request with grouped notifications; do not loop single-review calls for batch decisions.
 - `feedback move|comment|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. `feedback move --feedback-ids` sends one batch board move request.
 - `feedback comment` creates text-only feedback-specific comments. Attachments remain web UI only for this project-key endpoint.
@@ -116,13 +121,15 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `feedback validate|apply` remains available for validation and owner-direct apply paths.
 - `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.
 - 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.
-- 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.
-
-Release certification uses the shipped
-`scripts/project-assistant-live-full-harness.js`. Its default mode is network-free
-and accounts for all 38 project-key routes. Live mode is pinned to GaahField,
-requires explicit mutation flags, exercises concurrent idempotency, and delegates
-cleanup only to the existing exact-ID mission and Feedback harnesses.
+- 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.
+
+Release certification uses the shipped
+`scripts/project-assistant-live-full-harness.js`. Its default mode is network-free
+and accounts for all 38 project-key routes. Live mode is pinned to GaahField,
+requires explicit mutation flags, exercises concurrent idempotency, and delegates
+cleanup only to the existing exact-ID mission and Feedback harnesses.
+The harness uses the canonical `https://api.myte.dev/api` base and recognizes
+the live project's `Gaahfield MarketPlace` title as the governed GaahField target.
 
 ## Approval Artifact Requirements
 
@@ -130,7 +137,7 @@ Only selected project-key writes require a local approval artifact. The CLI adds
 
 | Category | Commands | Artifact |
 | --- | --- | --- |
-| Required | `create-prd`, `update-team`, `update-owner`, `update-client`, `feedback submit`, `feedback revise`, `feedback comment`, `suggestions create`, `suggestions revise` | Yes |
+| Required | `create-prd`, `update-team`, `update-owner`, `update-client`, `feedback submit`, `feedback revise`, `feedback comment`, `feedback tickets create/update/coverage`, `suggestions create`, `suggestions revise` | Yes |
 | Not required | `run-qaqc`, `mission status`, `mission archive`, `suggestions review`, `feedback review`, `feedback move`, `feedback undo`, `feedback apply` | No |
 | Never required | `config`, `query`, `bootstrap`, `sync-qaqc`, `feedback-sync`, `suggestions sync`, `feedback get/history/reviews/prd-versions/prd-diff/validate`, local feedback draft commands | No |
 
@@ -199,9 +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.
+- 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
 
@@ -218,8 +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.
+- `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
@@ -280,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
 
@@ -332,6 +348,10 @@ After `bootstrap`, find ids locally:
 | `feedback review` | Approves, rejects, requests changes, or cancels one review request, or a batch with `--request-ids`. | No approval artifact required; backend restricts approval/review decisions to Project Owner or elevated delegate for Feedback scope; batch review uses one grouped notification path. |
 | `feedback move` | Moves a card or batch of cards across allowed board states directly with an audit event. | No approval artifact required. `--feedback-ids` sends one batch request. Blocked with `pending_feedback_review` while an active linked review request exists; governed states such as archive/reject/deploy/freeze remain backend-authorized. Project-key unarchive is not supported. |
 | `feedback comment` | Creates a text-only comment on one Feedback item. | Requires `--confirm-write --approval-artifact <path>`; backend checks project-key access, owner/assigned permission, idempotency, and the 500,000-character content cap. Attachments remain web UI only. |
+| `feedback tickets list` | Lists engineering subtickets linked to one Feedback/PRD. | Read-only and included in `feedback-sync` for IDE discovery. |
+| `feedback tickets create` | Creates one ticket or one JSON/YAML batch. | `--dry-run` validates without mutation; live batches are approval-gated, idempotent, capped at 100 and return receipts. |
+| `feedback tickets update` | Updates one ticket or many `--ticket-ids` in one revision-fenced batch. | The backend validates the whole batch before mutation and returns `409` for stale revisions. |
+| `feedback tickets coverage` | Changes one ticket's coverage for one retained PRD document. | Synchronous, revision-fenced and approval-gated. |
 | `feedback undo` | Reverses an audited board event when there is no conflict. | No approval artifact required; backend validates event ownership/project scope and conflict state. |
 | `feedback prd-versions` | Lists retained PRD baselines/revisions for a feedback item. | Read-only; old S3 objects are retained by reference. |
 | `feedback prd-diff` | Fetches backend-generated text diff for PRD versions. | Read-only; backend controls version access. |
@@ -362,6 +382,7 @@ Read/sync routes:
 - `GET /api/project-assistant/bootstrap`
 - `GET /api/project-assistant/qaqc-sync`
 - `GET /api/project-assistant/feedback-sync`
+- `GET /api/project-assistant/feedback/<feedback_id>/tickets`
 - `GET /api/project-assistant/feedback/<feedback_id>`
 - `GET /api/project-assistant/feedback/<feedback_id>/refinement/history`
 - `GET /api/project-assistant/feedback-review-requests`
@@ -394,6 +415,13 @@ Mutation routes:
 - `POST /api/project-assistant/feedback/<feedback_id>/board-move`
 - `POST /api/project-assistant/feedback/batch-board-move`
 - `POST /api/project-assistant/feedback/<feedback_id>/comments`
+- `POST /api/project-assistant/feedback/<feedback_id>/tickets`
+- `POST /api/project-assistant/feedback/<feedback_id>/tickets/batch`
+- `POST /api/project-assistant/feedback/<feedback_id>/tickets/batch/validate`
+- `PATCH /api/project-assistant/feedback/<feedback_id>/tickets/<ticket_id>`
+- `PATCH /api/project-assistant/feedback/<feedback_id>/tickets/batch`
+- `POST /api/project-assistant/feedback/<feedback_id>/tickets/batch-update/validate`
+- `PATCH /api/project-assistant/feedback/<feedback_id>/tickets/<ticket_id>/prd-coverage`
 - `POST /api/project-assistant/feedback/<feedback_id>/events/<event_id>/undo`
 - `POST /api/project-assistant/suggestions`
 - `POST /api/project-assistant/suggestions/revise`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "myte",
-  "version": "0.0.55",
+  "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.55"
+    "@mytegroupinc/myte-core": "0.0.57"
   }
 }