myte 0.0.47 → 0.0.49

package/README.md

@@ -19,23 +19,34 @@ No install:
 
 - `npx myte@latest ...`
 
-`npm install myte` does not add `myte` to your shell `PATH`. Use `npx myte` or `npm exec myte -- ...` unless you installed globally.
-
-## Requirements
-
-- Node `18+`
+`npm install myte` does not add `myte` to your shell `PATH`. Use `npx myte` or `npm exec myte -- ...` unless you installed globally.
+
+The npm line `added N packages` is a dependency-graph count, not a count of
+files or Myte features. The public `myte` package is a small command wrapper,
+`@mytegroupinc/myte-core` contains the CLI implementation, and `undici`
+provides portable proxy support. A fresh `0.0.48` install therefore normally
+contains three graph nodes; npm may report fewer on an update when dependencies
+are already present or deduplicated. Run `myte info` or
+`myte --version --verbose` to inspect the exact topology.
+
+## Requirements
+
+- Node `18.17+`
 - macOS, Linux, or Windows
 - `MYTE_API_KEY=<project_api_key>` in your shell or workspace `.env`
 - `MYTEAI_API_KEY=<inference_api_key>` only for `myte ai`
 - `MYTEAI_API_KEY=<inference_api_key>` for `mytecody`
 - `git` in `PATH` only for `query --with-diff`
-- No runtime npm dependencies beyond the Myte packages themselves.
+- Standard `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` variables are honored
+  through the core transport dependency.
 
 The CLI searches for `.env` in the current folder and then up parent directories.
 
 ## Common Commands
 
-- `npx myte config --json`
+- `npx myte config --json`
+- `npx myte doctor --json`
+- `npx myte info`
 - `npx myte bootstrap`
 - `npx myte sync-qaqc`
 - `npx myte feedback-sync`
@@ -60,8 +71,9 @@ The CLI searches for `.env` in the current folder and then up parent directories
 - `npx myte feedback apply --file ./MyteCommandCenter/reviews/feedback/<id>-edit.yml`
 - `npx myte suggestions sync`
 - `npx myte mission archive --mission-ids "M001" --reason "Duplicate disposable mission"`
-- `npx myte query "Summarize the current branch changes" --with-diff`
+- `npx myte query "Summarize the current branch changes" --with-diff --json`
 - `npx myte create-prd ./drafts/auth-prd.md --confirm-write --approval-artifact ./drafts/auth-prd.md`
+- `npx myte create-prd ./drafts/proposal.md ./drafts/harness.md ./drafts/security.md --document-set --confirm-write --approval-artifact ./drafts/approval.md`
 - `npx myte update-team "Backend deploy completed." --confirm-write --approval-artifact ./updates/team.md`
 - `npx myte update-owner --subject "QAQC progress" --body-file ./updates/owner.md --confirm-write --approval-artifact ./updates/owner.md`
 - `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md --confirm-write --approval-artifact ./updates/week-12.md`
@@ -72,6 +84,17 @@ The CLI searches for `.env` in the current folder and then up parent directories
 
 ## Behavior
 
+- `doctor` performs read-only package, credential-presence, DNS, direct
+  TCP/TLS, authenticated config, proxy, and workspace checks. It reports the
+  failing layer without printing the API key, proxy URL, request body, or
+  response body.
+- Network failures distinguish DNS, TCP, TLS/certificate, timeout, captive
+  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.
 - `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.
 - `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.
@@ -119,7 +142,13 @@ Minimum artifact contents:
 Batch guidance:
 
 - Mission edit/create batches use `myte suggestions create` or `myte suggestions revise`. The artifact must list each item. For edits include `change_type: update`, the existing `mission_id`, and changed fields. For new missions include `change_type: create`, title, description, and acceptance details. For revisions include each `suggestion_id` and expected revision.
-- PRD batches use one `myte create-prd fileA.md fileB.md ...`; the artifact must list each PRD file/title/client ref and `batch_count` must match the number of PRD items.
+- Without `--document-set`, `myte create-prd fileA.md fileB.md ...` preserves
+  the existing behavior and creates one independent Feedback item per file.
+- With `--document-set`, one to three Markdown files create one Feedback item
+  with ordered, independently readable PRD documents. Each document is
+  validated locally against the 250,000-character server contract. The
+  approval artifact must list every file/title/client ref and the matching
+  document count.
 - Feedback submit/revise/comment artifacts are usually the same YAML or markdown file being submitted. If the command uses inline text or stdin, create a separate approval memo with the feedback id or request id and exact content.
 - Team, owner, and client update artifacts should name the audience and include the exact message body or a complete summary. Client updates should include target contact ids when used.
 - `feedback review --request-ids`, `feedback move --feedback-ids`, `mission status --mission-ids`, `mission archive --mission-ids`, and `run-qaqc --mission-ids` are batched governed writes, but they are marked `Not required` and should not receive approval artifact flags.
@@ -141,7 +170,7 @@ Recommended agent flow:
 1. Run `myte config --json` to confirm the project, API base, configured repos, and local workspace detection.
 2. Run `myte bootstrap --json`, `myte feedback-sync --json`, or `myte sync-qaqc --json` to hydrate local context under `MyteCommandCenter`. `bootstrap` also writes `MyteCommandCenter/AgentsMyteAPI.md`, the local action matrix agents should consult before mutating Myte state. Use `myte suggestions sync --json` only for narrow mission-review refreshes after bootstrap.
 3. Use `myte query "<goal/evidence/ask>" --with-diff` when local code changes matter.
-4. Use `myte create-prd <file.md> --confirm-write --approval-artifact <path>` 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.
+4. Use `myte create-prd <file.md> --confirm-write --approval-artifact <path>` only after the PRD markdown has been reviewed by a human. Add `--document-set` for one parent with up to three ordered documents. Without that flag, multiple files remain independent PRDs. The file body is the PRD document; `--description` is only the short board/card summary.
 5. Use `myte feedback status|edit|assign|archive|refine` to create reviewable local artifacts. `feedback submit` and `feedback revise` require an approval artifact; `feedback review` does not because the backend owner/delegate review membrane is the approval control.
 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.
 7. Use `myte suggestions create|revise|review` for mission review threads. `suggestions create` and `suggestions revise` require an approval artifact; `suggestions review` does not because the backend Project Owner/elevated-delegate decision is the approval control. Valid create `change_type` values are exactly `update` and `create`; revisions keep the existing thread type and must not include `change_type`.
@@ -157,7 +186,33 @@ PRD document contract:
 - The UI renders the PRD from the stored document text, not from the card description.
 - 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.
+- 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.
+
+## Connectivity Diagnostics
+
+Run this before assuming an API key or server failure:
+
+```bash
+myte doctor --json
+```
+
+Interpret the first failed layer:
+
+- `dns`: the API hostname could not be resolved.
+- `tcp`: the host resolved but port 443 could not be reached.
+- `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.
+
+On restricted Wi-Fi, complete any captive-portal login, configure the
+network's supported proxy/VPN, or retry on another network. The CLI honors
+`HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY`; it never recommends disabling
+certificate verification.
 
 Preferred file shape:
 

package/package.json

@@ -1,24 +1,28 @@
 {
   "name": "myte",
-  "version": "0.0.47",
+  "version": "0.0.49",
   "description": "Myte developer CLI.",
   "type": "commonjs",
   "license": "MIT",
   "files": [
-    "README.md",
-    "THIRD_PARTY_NOTICES.md",
-    "TRADEMARKS.md",
-    "bin",
-    "package.json"
+    "README.md",
+    "THIRD_PARTY_NOTICES.md",
+    "TRADEMARKS.md",
+    "bin",
+    "scripts",
+    "package.json"
   ],
-  "bin": {
-    "myte": "bin/myte.js",
-    "mytecody": "bin/mytecody.js"
-  },
-  "engines": {
-    "node": ">=18"
+  "bin": {
+    "myte": "bin/myte.js",
+    "mytecody": "bin/mytecody.js"
+  },
+  "scripts": {
+    "postinstall": "node scripts/postinstall.js"
+  },
+  "engines": {
+    "node": ">=18.17"
   },
   "dependencies": {
-    "@mytegroupinc/myte-core": "0.0.47"
+    "@mytegroupinc/myte-core": "0.0.49"
   }
 }

package/scripts/postinstall.js

@@ -0,0 +1,8 @@
+#!/usr/bin/env node
+
+console.log([
+  "Myte CLI installed successfully.",
+  "Included: myte and mytecody commands, the Myte API client, and portable proxy support.",
+  "The MyteCody engine and client assets are downloaded on first `mytecody` coding run.",
+  "Run `myte --help` to get started.",
+].join("\n"));