@native-engagement/cli 0.8.2 → 0.9.1

package/package.json

@@ -1,23 +1,17 @@
 {
   "name": "@native-engagement/cli",
-  "version": "0.8.2",
+  "version": "0.9.1",
   "type": "module",
-  "description": "Authenticated Native Engagement command line client",
   "engines": {
     "node": ">=24.22.1 <25"
   },
-  "license": "UNLICENSED",
+  "license": "Apache-2.0",
   "files": [
     "dist",
-    "README.md",
+    "LICENSE",
     "release.json",
     "THIRD_PARTY_LICENSES.txt"
   ],
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/SENLIN746/native-engagement.git"
-  },
-  "homepage": "https://engagement.shipkitx.com/downloads",
   "publishConfig": {
     "access": "public",
     "tag": "beta"

package/release.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "sourceCommit": "0270865d1f69c5c4c01d3acab37090346699763a",
+  "sourceCommit": "bc4ff2a04ed51d004904430cabe24b6a739f88e8",
   "channel": "beta",
   "bundledComponents": [
     {
@@ -14,5 +14,5 @@
       "license": "MIT"
     }
   ],
-  "lockSha256": "6fed06159024d6c915e45acdd81734e0ec37fc25230cb6c1a9c00013d7a2ed66"
+  "lockSha256": "00164f8922c82350ad7cbe357f976d03b46faec9ebe48c634cb8ba2a922c3e3c"
 }

package/README.md

@@ -1,54 +0,0 @@
-# Native Engagement CLI
-
-Node.js 24.22.1+ (24 LTS) client for the Native Engagement HTTPS service.
-
-```sh
-npm install --global @native-engagement/cli@0.8.2
-native-engagement --version
-native-engagement login
-native-engagement auth status
-```
-
-## Account and password sign-in
-
-`login` opens your system browser. Enter your account, password and any MFA challenge on the identity service's page and approve the requested permissions. OAuth Authorization Code with S256 PKCE returns the result to the CLI on loopback. A current browser SSO session can avoid repeated password entry. Your administrator must provision your account and tenant permissions first.
-
-The default center is https://engagement.shipkitx.com. Use `NATIVE_ENGAGEMENT_API_URL` for another trusted HTTPS center. The browser callback must reach the machine running the CLI. For an application-managed browser on macOS/Linux, run `native-engagement login --no-open`: stderr reports the path of a private `authorization-url.txt` file. Open its URL in a browser on this machine; the file is removed on completion or cancellation. Authorization URLs and passwords are not printed in command results. `NATIVE_ENGAGEMENT_CLI_HOME` selects an absolute private current-user directory.
-
-The access grant uses a private current-user file on macOS/Linux and current-user DPAPI on Windows. Refresh tokens are not persisted. Run `login` again after expiry. `native-engagement logout` revokes and removes the grant. Login requests engagement read/write, work read, asset read and message draft, intersected with current tenant permissions. Desktop installation and identity administration use their own authorization.
-
-For automation, supply a separately authorized short-lived `NATIVE_ENGAGEMENT_BEARER_TOKEN` through the protected environment. Password, token and principal overrides are not accepted in argv. An npm publishing token is unrelated to service login.
-
-## Complete prospect workflow
-
-```sh
-native-engagement schema get prospect.batch.import
-native-engagement prospect preview --input @import.json
-native-engagement prospect import --input @import.json
-native-engagement prospect batch --input @batch.json
-native-engagement prospect company --input @company.json
-native-engagement prospect engage --input @engage.json
-native-engagement prospect engagements --input @association.json
-native-engagement prospect batches --input @page.json
-```
-
-Inputs follow the canonical schemas from `schema get`. `import.json` supports country, industry, address, contact name/title and original score in each row's optional `profile`; the SDK README has a complete input. Source URLs are optional; provide an actual credential-free HTTP(S) page when known. Preserve source reference/version, observation time and current/historical status. Original research and verification stay with their owner; Native stores observations and receipts.
-
-`batch.json`: `{"batchRef":"YOUR_BATCH_REF"}`. `company.json`: `{"prospectRef":"YOUR_EXACT_PROSPECT_REF"}`. `engage.json` selects the exact imported CURRENT contact/source observation and supplies an engagement reference, why-fit/why-now and stable idempotency key. Creating an engagement does not send or schedule work. Retry an unchanged input with its original key.
-
-`association.json`: `{"prospectRef":"YOUR_EXACT_PROSPECT_REF","limit":20}`; pass returned `nextCursor` as `cursor`. `page.json`: `{"offset":0,"limit":20}`; continue with `nextOffset` until null. Batch history has no 100-total cap; responses contain at most 100 records. `prospect list` queries the company catalog.
-
-```sh
-native-engagement contracts list
-native-engagement query <contract-name> --input @request.json
-native-engagement command <contract-name> --input @command.json
-npx @native-engagement/cli@0.8.2 --help
-```
-
-Results are JSON: exit 0 success, 2 rejected input/access, 1 unavailable. Unknown external effects require original-operation inspection before retrying. Local execution nodes and channel authorization use the Desktop installation flow.
-
-## MCP OAuth
-
-Connect your MCP host to `https://engagement.shipkitx.com/mcp` using Streamable HTTP and OAuth. It discovers the authorization server from the 401 resource-metadata challenge, opens its own browser sign-in and receives its own grant. The center currently uses pre-registered MCP clients with exact registered callbacks. Ask your administrator to register the host first if it has no client configuration; the CLI client identifier is reserved for the CLI/SDK loopback flow. Current directory permissions govern each MCP call.
-
-This beta uses license `UNLICENSED`. [Complete account and OAuth guide](https://engagement.shipkitx.com/releases/authentication.md) · [Downloads](https://engagement.shipkitx.com/downloads)